At every start of a .net program using the .net driver for SQLA the file dbdata16.dll is written again. This will usually be checked by any anti virus software. On a server system with multiple background programs this behavior generates an unnecessary workload. Just a sidenote: even when the DLL is already loaded, the programs will search for it afterwards in the GAC.
|
A fix is forthcoming that will change this behavior. If the dbdata DLL is present, the provider will load it and do a version check. If that passes, it will use it. If not, then it will try to delete it, and then move on. Tip: Currently, the provider attempts to delete the DLL first and, if this fails, then it will load it and check the version. So if you make the DLL read-only, you will get the behaviour you are looking for. Strange but true. |
I'd think that this is at least documented behaviour:
I know, therefore I asked for a feature change
Unfortunately still true for SQLA 17
http://dcx.sybase.com/index.html#sqla170/en/html/3bcf66b76c5f1014b219867750fa0899.html
Re: Just a sidenote: even when the DLL is already loaded, the programs will search for it afterwards in the GAC.
I cannot see this behavior.