Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
95swappedsi
Starting Member
3 Posts |
 Posted - 2008-05-06 : 22:51:38
|
| This may not be the correct forum for this, but has anyone ever seen an issue with Concat_null_yields_null being set to off when the application opens the database connection yet random connections exhibit behaviors as as if Concat_null_yields_null was set to on. If the user logs out of the application and back in getting a new SID the issue no longer occurs. It almost seems like Session pooling is occuring and the application connection sets the Concat_null_yields_null off but then jumps to a session from the pool that has Concat_null_yields_null ON some other sessions may not require the concat setting to be off...possibly services or who knows. I have been told by our developers that we have session pooling off, but it seems that SQL Server 2000 may have issues with pooling.... I am not a developer or a DBA, but I am trying to track down thiis issue. I know one such chas I modified one SP to use isnull where conactionation was taking place and the issue for the session seemed to go away, and apparently there is no way to check the session settings of a session in the DB other than the current session....Any thoughts or ideas???? Thanks in advance |
|
|
|
|
|
Set Concat_null_yields_null off