Definitely worth noting. For Standard, you can still use Mirroring or Log Shipping, if you can handle a delay.

It sounds like you're using a trigger, which won't have a clue as to what timezone the client is located.

Since you already have the timezone offset, don't use GETDATE. ...

How are you generating the audit trail?

EDIT: If you know the timezone, then you should know the offset. Use TODATETIMEOFFSET:

http://msdn.microsoft.com/en-us/library/bb630335(v=sql.100).aspx

Are you recording timezones anywhere in your audit trail? If not, having the times recorded in differing timezones is going to leave your audit trail useless.

While I agree you shouldn't create a proxy for a standard user account, I see no problem with creating a proxy for a service account. I have done this...

PHXHoward (8/23/2012)

---

Thanks for the example.

I have made a script to do what I believe you indicated.

DECLARE @cmd1 varchar(500), @cmd2 varchar(500), @cmd3 varchar(500)

SET @cmd1 = 'print ''[?]'''

SET @cmd2 = 'IF ''[?]''...

You cannot assign a proxy directly for TSQL steps.

You have two options:

1. Create an operating system proxy, and use sqlcmd to execute the TSQL.

2. Create a Powershell proxy...

You can run multiple instances versions on a cluster node or even a standalone host, as long as the underlying OS supports that version.

In any case, I make an attempt...

While you'll likely receive varying opinions on this subject, my advice is to start reading and configure a test instance to apply what you're reading. Microsoft makes the AdventureWorks...