Search results for query: *

If anyone finds a solution for this, please let us know - we're having the same problem. Thanks, Pete Cousins

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)

...the tables using SHOW CONTIG and DBCC DBREINDEX in the original system but this halved processing time on all servers involved. Use Master /****** Object: Database PerfTest Script Date: 23/06/2006 12:07:28 ******/ IF EXISTS (SELECT name FROM master.dbo.sysdatabases WHERE name =...

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...

...Begin Action: DialogShowSdComponentMult 14:17:27 basesys = 0, baseinst = 0, basedata = 0 14:17:27 Begin Action: Component Handler 14:17:27 ***** Silent Mode in Multi comps 14:17:27 [SQLComponentMult] 14:17:27 Result = 1 14:17:27 ComponentSelectItem(MgtTool\Wzcnflct): -103 14:17:27 End...

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...

...Blocks. 2005-09-05 14:18:35.78 server Attempting to initialize Distributed Transaction Coordinator. 2005-09-05 14:18:37.23 spid3 Warning ****************** 2005-09-05 14:18:37.23 spid3 SQL Server started in single user mode. Updates allowed to system catalogs. 2005-09-05...

Thanks for people looking at this post. I've resolved 2 out of 3 of the problems as follows: 1) SQL Server Memory link on our branches was caused by an in-house NT Service written using Dot Net. I now stop this service in the evening, and restart it in the morning - no more memory problems and...

I have warned management about this on several occasions, but as we're 'nice and safe' behind our firewall, with draconian restrictions on e-mail attachments and use of floppy disks and cd-roms, they've decided it's not a worry. Of course, if I was an external consultant, and they'd paid me...

Although I personally hate them, you could also do this with a correlated subquery. Something like: Update tbldata set DaysBetweenTrips= datediff(D, DayShopped, (select max(Dayshopped) from tbldata b where b.customer=a.customer and b.dayshopped<a.dayshopped)) from tbldata A The syntax probably...

This is a tough problem, so I could do with some help from you SQL Gurus (Terry - I hope you're reading this). We have 115 SQL Servers in branches throughout the UK. They are running Windows NT 4 SP6, SQL Server 2000 SP2. Over half of them are having Blue Screen errors and automatically...

I am looking at an identical problem - 3rd party software even. BOL indicates the other reason for running out of locks may be due to insufficient memory - no matter how high your lock limit it, it will always be restricted by the available memory. The other way to reduce locks is to run the...