May 9, 2005 at 4:51 am
I hope someone can help me here. We recently swicthed from a NT server to a Win2K machine running SQL 7.0 and the new server is running very slow. The initial problem we faced was that authentication failed because we swictched over the server names so to work around it we are having to use named pipes. I have a .net web app that runs on another server with SQL 2K on it which calls a stored proc with a link to the SQL 7.0 box. The unusual thing we see when running profiler over the SQL 7.0 box is lots of sp_cursorfetch calls - which are not called explicitly within my sp or web app. We didnt have this problem when we were on the old server. Any help would be most appreciated. Thanks
Just to add: I would like to convert this to SQL 2K if possible - the issue we have is the fields of data type "bit" which are stored as 0 or -1 in SQL 7 and 0 or 1 in SQL 2K. What's an easy way of getting around this issue?
May 10, 2005 at 2:34 pm
One of the reasons for sp_cursorfetch calls are because of server side cursors. Below is an excellent article explaining the same.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply