Viewing 15 posts - 56,851 through 56,865 (of 59,098 total)
Text files of this nature are easy to load and you don't need BCP or any of that so long as you have the right privs...
Let's say you have...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2007 at 11:07 pm
It's correct... there is a very minor amount of logging for Temp Tables and none for table variables. The fact that Temp Tables can use statistics and Table Variables cannot...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2007 at 4:53 pm
Emphasis... when a session is completed, the Temp Tables are automatically dropped. I don't believe there's a way for you to loop through TempDB to figure out which are "yours". ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2007 at 4:48 pm
I prefer Remi's solution... shorter transaction... fewer actions within the transaction... maybe fewer deadlocks.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2007 at 4:44 pm
Oh, be careful... I could be wrong but I'm thinking that if you have an insert of more than one user, you'll only get one value for @user_ident for that...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2007 at 6:27 am
Hoooo-boy! Do I understand that! My rants peel paint, knock bricks out of old buildings, and embarrasses seasoned sailors
not to mention causing...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2007 at 6:16 am
About the only thing I'd change is I'd remove the declared transaction.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2007 at 6:08 am
Like table variables and some views, temp tables use memory and spill over into temp db disk space if they get too big. It's a good idea to have a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2007 at 6:01 am
Any translation of a DATETIME to anything character based or though most UDF's will be slower than doing some simple math using date functions... try this...
WHERE TransactionDate >= DATEADD(dd,DATEDIFF(dd,0,@TDate),0)
...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2007 at 11:25 pm
One picture is worth a thousand words... great explanation...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2007 at 11:17 pm
Nicely done, Remi...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2007 at 11:15 pm
Running the code to create a stored procedure is not the same as running a script... the stored procedure will allow for "deferred naming" until runtime. This is so you...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2007 at 11:12 pm
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=348736#bm348757
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2007 at 11:05 pm
Heh... first, I'm not into "biting balls"
And, I'd have to say "lack of planning on somebody's part, did constitute and emergency on...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2007 at 10:58 pm
I can't really imagine assigning all users to every new project and vice versa... but, if you must, put a trigger on the User and Project tables that does it...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2007 at 10:33 pm
Viewing 15 posts - 56,851 through 56,865 (of 59,098 total)