You're seeing the correct behaviour - triggers are fired once per batch, not once per row. You can never assume that only a single row will be deleted at a...

You're not really missing anything. Dropping the buffers basically gives you a worst-case scenario as to how your query will perform, and will test your I/O subsystem (assuming no I/O...

Thanks for the clarification, Jon. I didn't have the same setup available to give it a quick test, and had a niggling though that it would exhaust a single log...

Great editorial, Steve. You can't make solid, durable furniture (or databases) without logging!

Hi Vardan,

Welcome to SQLServerCentral, and the wonderful world of being a SQL Server DBA.

You've posted this message in the Integration Services 2005 forum, and an architecture document for this...

If the last batch was two weeks ago, and they query is AWAITING COMMAND, then it is most likely inactive. It's possible that it has a transaction open and is...

I'll have to run some tests to validate the following, but it sounds likely.

If you have created your log files at one time, a long time ago, and configured each...

Hi Nic,

I ran into this issue today. As this was a top search result in Google for the error message, I figured I'd share.

The issue is that in 2005+, SQL...

While the tools are typically 32 bit, the installation package in the x64 version won't install onto a 32 bit operating system. Every DVD I've seen has had all...

Allow database locations to be stored in Active Directory. I want to my connection string to point to "AdventureWorks", and AD should be consulted to determine which server/database to...

Hi Walton,

Here's some example code, with comments.

CREATE TABLE #t1 (Value int, Item char(1))

INSERT INTO #t1

SELECT 1, 'A'

UNION ALL SELECT 1, 'A'

UNION ALL SELECT 1, 'B'

UNION ALL SELECT 2, 'B'

UNION ALL...

Hi Andrew,

I don't believe there is a specific role other than sysadmin. The individual permission is ALTER TRACE:

GRANT ALTER TRACE TO [Domain\Account]

Books Online: http://msdn.microsoft.com/en-us/library/ms187611(v=SQL.90).aspx

This isn't quite robust enough. If new rows are inserted during your SELECT operation, you may or may not end up with them in the archive table, which means...

Delete performance is dependent on two factors: how quickly you can identify the rows to be deleted, and how quickly you can delete the row. Make sure you're testing...

I have never tried using the built-in log shipping tools to go from 2000 to 2005, but custom scripts (backup log on 2000 and restore on 2005) definitely works. ...