well, the problem first happened last thursday, and we were on sp1. we rebuilt the cluster over the weekend and upgraded to sp2, and that didn't fix the issue. microsoft...

well, I think we have eliminated hardware as the issue. Over the weekend, we rebuilt the cluster on new hardware and even a new location on the SAN for the...

yeah, we have run profiler, and didn't find an increase in load. We even have a case open w/ microsoft since friday and they have not come up with anything...

there is no long running transactions or blocking going on. TempDB is failry small (under 1 GB). I am unable to find the counters for sql server in perfmon. Not...

well, It just throws a generic asp error. I ran a trace and the app connects, but never sends any commands through. I also traced for exceptions and found none.

SELECT * FROM msdb.dbo.[backupset] WHERE database_name = 'databasename' AND TYPE = 'l'

that is the limit of recursion for stored procedures. a sproc can only call itself 32 times before SQL suspects it may be an infinite loop and terminates it.

check this...

this should get you started:

CREATE TRIGGER ddl_trig_database

ON ALL SERVER

FOR CREATE_DATABASE

AS

PRINT 'Database Created.'

SELECT EVENTDATA().value('(/EVENT_INSTANCE/TSQLCommand/CommandText)[1]','nvarchar(max)')

yes, both of those statements are just fine. Be aware of the consequences you could face by using nolock (dirty reads, etc.)

I always use sequel just because it's easier for me to say it that way

you will need to play with it a bit to get the right format(server name, then date) or change the format of the date, but this should get you going....

I think method #2 or #3 in this article would be what you want to do.

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

you could use the file system task to delete the file and recreate it first, but there should be an easier solution I would think

detach the databases on the old server, copy the data and log files to new location, then attach on new server.

Another way I like to do it is just...

we had the same thing happen to us when we migrated to 2005. We never did find a solution. We used it for log shipping to see how many logs...