What OS and SP are you running ? What version of SQL and SP are you running ? Have the maintenance plans ever functioned correctly on the instance in question...

What version and SP is your cluster OS ? We presently have a few active/passive clusters running SQL 2KSP3a. We upgraded most of them from WIN 2K/SP4 to Win 2K3/SP1...

Database files on a SAN. The benefits of the SAN are the redundancy, the fiber-channel architecture, the ability to use many disk spindles thus distrinbuting I/O more effieciently and the...

It sounds like you are using the Veritas SQL Agent and not doing 'true' backups. At our shop, and many in the pasy that I have worked at, we have...

The information has to be 'cached' somewhere. Either the portal machine or the computer using the portal. There is no way the database on the old server could be accessed...

truncatin logs page allocations/deallocation as opposed to rows for a delete. Still logging, just less.

NASA gave us Tang in the 60's, the DOD via the Manhattan project gave us Teflon in the 40's. Which is more valuable today ?

(This really ought to stir things...

We need a 'war stories' category ... I'm sure there would be lots of contributions ... not to mention 'spirited' discussion as well ...

We need a 'war stories' category ... I'm sure there would be lots of contributions ... not to mention 'spirited' discussion as well ...

NO. Everything is logged <period> It's just whether or not the data in the log is cleared (dependent on the receovery mode).

yup ... you mught want to even couple it with the 'undocumented' stored procedure sp_MSforeachtable

http://www.databasejournal.com/features/mssql/article.php/3441031

Be careful though ... the majority of this post used 'imlpicit' conversions. Experience has taught that 'implicit' (like 'default') can get you into trouble when you least expect it. Just...

It sounds like a local computer issue to me. I just went through more than 91 entries a couple of times after first doing your search for 'trigger' ...

Here's my process:

• make a full backup
• script out the schema (sometimes even bcp out the data table by table - accounting departments love this)
• stick the database in 'read only' mode for...

you could also try something with smaller units of work to allow the transaction log to 'clean' itself ...

set rowcount 10000                          --> this allows only 10,000 rows to be deleted

go

declare...