E
Evan Stone
Has anyone here done any benchmarking with the iAnywhere.Data.AsaClient
provider versus using System.Data.Odbc (or Oledb for that matter)?
Initially I thought that the iAnywhere provider was going to be the
better way to go, but in learning that it's just a .NET dll layer
(iAnywhere.Data.AsaClient.dll) over a Win32 DLL (dbdata9.dll), I was
just wondering how much it would buy us.
<thinking_out_loud>
Additionally, it seems that if we want to use other databases (like
SQLServer, for instance), then our best bet for compatibility is to use
the ODBC provider (and use T-SQL).
</thinking_out_loud>
Does this all sound reasonable, or am I way off base here?
Thanks!
-Evan
provider versus using System.Data.Odbc (or Oledb for that matter)?
Initially I thought that the iAnywhere provider was going to be the
better way to go, but in learning that it's just a .NET dll layer
(iAnywhere.Data.AsaClient.dll) over a Win32 DLL (dbdata9.dll), I was
just wondering how much it would buy us.
<thinking_out_loud>
Additionally, it seems that if we want to use other databases (like
SQLServer, for instance), then our best bet for compatibility is to use
the ODBC provider (and use T-SQL).
</thinking_out_loud>
Does this all sound reasonable, or am I way off base here?
Thanks!
-Evan