Viewing 15 posts - 57,466 through 57,480 (of 59,101 total)
Peter,
Thanks for being patient with the explanation... It would be really nice to combine both methods so that if something other than your proc fires the trigger, you can still...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2006 at 7:38 pm
Yep, sorry about that... I got a little frustrated with you... everyone has been trying to tell you that you're asking for "Death by SQL" by doing the UPDATE right...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2006 at 8:29 am
There's really no physical problem to keep you from using it... However, Microsoft and a bunch of folks on this forum have indicated that in order to guarantee that your...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2006 at 7:27 am
I guess I'm just going to have to materialize this code and test it...
Would you post the CREATE TABLE statement for the two audit tables and the CREATE FUNCTION...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2006 at 7:21 am
And, you need to be real careful if this comes anywhere near a GUI... think "SQL Injection". Theres a huge amount of info on how to prevent it... do a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2006 at 7:15 am
I guess I don't understand... obviously, you are finding the correct Windows user name somewhere along the line in your stored procedure because you want to "pass it" to a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2006 at 7:11 am
It's the triple quotes in the variable assignment that are the most recent problem...
Try this...
declare @townID varchar(25),
@sql varchar(1000)
set @townID = '00003' --<<THIS IS WHERE THE...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2006 at 6:49 am
Old guys rule...
1 million conversions... 11 seconds... works for positive numbers, negative numbers, zero, and NULL...
DECLARE @Places INT
SELECT TOP 1000000...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2006 at 1:51 am
If you run this code, you might just want to have your DBA turn on Trace Flag 1204 just to be safe ![]()