We've found the solution, and just list it here for completion.
It transpires that the SP is failing on the same statement every time - but the previous statement varies depending on parameters. The statement that is failing is a DELETE from a table that has been dropped from the database. As...
Another update - the lastest failure is on a statement yet further on in the stored procedure. We're going to try and keep re-running it in the hope that eventually all the statements will work. Very bizzarre - never seen anything like this before.
A quick update - I've found the problem is in one stored procedure. The trace captured the fact that SQL server was recompiling the following statement inside the SP:
delete #matchGroupsCore
where ODSChannelId = @channelId
and ODSCoreId = @coreId
The paremeters are both int. However...
I was just wondering if anyone could help with the following problem. A batch process, that has been running fine, has started failing with 'Attempt to access expired blob handle (3).' and 'A system assertion check has failed', causing SQL Server to write a dump file, and this message in the...
The average disk queue length peaks at about 100 for the first phase, but after that it's sitting at just under 1 for the remainder of the query (the slow part) - this is true for when db is on SAN or local disk
Some more information after further testing. The average latch wait time of 1000ms is happening on the Server regardless of whether the database is on the SAN or the local drive. However, on the SAN the latch waits per second and page reads per second are both around the 100 mark, whereas on the...
Try looking at this webcast from Microsoft:
http://support.microsoft.com/kb/895614/en-us
It discusses I/O issues with SQL Server (& SANS).
I'm also having a problem with SAN performance for which I've started a seperate post (thread962-1249273)
I post my script here for completeness. Although I worked hard to write such bad SQL, believe me it is nowhere near as bad as the original query (3 pages of A4!!).
I recreate the database, and data tables at the beginning but this is quick - about 5 minutes. Most of the time is spent running the...
We have a 3rd party application which runs on a SQL Server box with a RAID drive. We attempted to move the database in question to a new SQL Server with all it's disk (apart from pagefile) on our NetApps SAN. One query in particular went from taking 35minutes to 2 hours 30 minutes. I have...
If it were a firewall problem, why would it work on the third set of identical disks?
Unfortunately, as the servers are being built remotely, I can't access the machine during the installation process.
We have built about 10 more servers without further problems. The only difference is that the...
You are correct. However, as I understand it, cnfgsvr.exe is starting SQL Server up for the first time, in order to change the password and configure it as per our requirements - this is part of the installation. We do not have a blank password for our SA accounts. In fact, once we've got all...
We have a strong password. The automatic install does SQL 2000 RTM first, and then SP4 after.
The thing is, it's working on about 50% of the machines - which are all identical specification. In fact, the installation etc. is on pre-built hard disks, with identical software, and these are just...
We're trying to install SQL 2000 (no SP) and then SP4 on Windows 2003 SP1. This is being installed automatically. However, the initial SQL 2K install is failing. The sqlstp.log has the following error message:
14:18:35 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.