Are you backing up the transaction logs? I suspect that you are only doing full backups, which will not affect the t-logs. Make sure that you are backing up T-logs.

The...

any error? event viewer should indicate where the problem is

The profiler should be on your server -

Start -> Programs -> Microsoft SQL Server 2005 -> Performance Tools -> SQL Server Profiler

Create new trace (File - New Trace ) and...

Hi

You could use SQL profiler - check the performance objects. Performance - Showplan XML gives a graphic of the query.

Don't run a profile for too long - it may hit...

Maybe worthwhile looking at the server logs to try to find when the file was lost. Also, our network people take reqular back-ups of the disks...

Hi

Saw this error message a while ago - the problem was not with the connections but with a query, which did not finish. The stuff about the connections in the...

AAAAAA. Knew there was something I'd missed.

Shouldnt this be

SELECT C.CATID, COUNT(*)

FROM #DATA DINNER

JOIN #CATEGORY C ON (C.VAL1 = DINNER.VAL1) OR (C.VAL1 IS NULL)

GROUP BY C.CATID

(was ON C.VAL1 = D.VAL1)

Had a CLR procedure cause random server crashes in production. Only able to replicate the error in Dev after a lot of work and never realy fixed.

If you can, avoid.

Hi

Not sure if it helps but

http://support.microsoft.com/kb/304261

seems to cover this

I've always restored the database and ran checkdb, then open a table ot two.

The verifyonly performs minimal checks - if you have the time and space I'd use the above...

you could use a tool (eg ssis) to move the data and objects from the 2K5 database to the sql2k database..

Not sure what problems you'd hit - I've only gone...

Thanks. I'll try to set up a test environment - if I get anywhere I'll post back.

Putting the application on its own SQL Server instance seems to have cleared the...

Hi thanks for the reply,

I'm running SP2.

I used the -G to reproduce the error - It's not set on the production system. I may have to use it, though. Not...

Hi

Thanks for the reply.

I've asked the programmers to check, but they are confident that the CLR is not leaving anything around.

(I don't have access to the code!)