Logging all activity to a table could be disastrous for performance. The recommended way to handle auditing is to write to...

If the owner's login is disabled in the instance then it can still successfully function as a database owner for things like cross-database ownership chains and such. Make sure none...

Or using the -v option.

sqlcmd Utility (SQL Server 2005)

Trace is going to be your best option on 2005. You could also look into C2 or Common Criteria auditing (which both use Trace by the way) as those are...

davery 28734 (1/28/2013)

---

I have a windows 2003 server running sql 2005 with a developer license installed. It's now in production. I have purchased the production license, but my...

On SQL 2005 Trace should work just fine. Most third-party tools will likely leverage Trace anyway. You can filter on SessionLoginName to capture all SQL text issued to the instance...

Kishore-132325 (1/28/2013)

---

Hello - Below is my setup :

1. 1 SQL Server 2012 [ destination server ]

2. 1 SQL Server 2008 [ source server ]

3. 1 File server - I...

Having AWE enabled allows the system to address up to 4GB of RAM, the actual limit for a 32-bit system. 2GB is the artificial limit based on how Windows divides...

IO_COMPLETION means the code is working but the database engine is waiting for the IO system to finish committing the transaction. It sounds like the system that it will not...

Are you sure there no DML triggers in play? Which exact build of SQL Server are you using?

SELECT SERVERPROPERTY('Edition') AS Edition,

SERVERPROPERTY('ProductVersion')...

winston Smith (1/28/2013)

---

issue resolved with a constraint on the date column. seems the engine is happy to do the swap if the constraint enforces only rows that can only go...

When you promote the new assembly into the GAC is it using the same version and public key?

You were also missing the END that matched the opening BEGIN. If you do not plan on doing any custom error handling, e.g. enriching the error message, in the trigger...

The fact that the code works on some systems and not others indicates the code is likely sound but that there may be an environmental factor in play preventing success...

It requires a bit of dynamic sql:

USE master;

DECLARE @dbname SYSNAME = N'AdventureWorks2008R2',

@filename NVARCHAR(500) = N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2DEV\MSSQL\DATA\AdventureWorks2008R2_Data.mdf',

@logfilename NVARCHAR(500) = N'C:\Program Files\Microsoft...