Viewing 15 posts - 50,191 through 50,205 (of 59,091 total)
So, the question would be...
... are you allowed to use CLR's on your system?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 3, 2008 at 9:52 pm
Haven't found the precise example I'm looking for, yet, but I did find this one... it's why so many people think recursion is a good thing... 😉
...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 3, 2008 at 7:17 pm
Sorry... forgot to post the results from above...
[font="Courier New"]SQL Server Execution Times:
CPU time = 2469 ms, elapsed time = 2628 ms.
SQL Server Execution Times:
...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 3, 2008 at 6:19 pm
Grant Fritchey (6/3/2008)
Amen to table variables and bad statistics. Especially table variables. I'd still love to see what Jeff's got on the subject.
I'm still trying to find the example with...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 3, 2008 at 6:16 pm
Nicely done, Ken... gonna add this one to my toolbelt... Heh, gotta find some way to get rid of the cursor, though (it's just me 😀 )
--Jeff Moden
Change is inevitable... Change for the better is not.
June 3, 2008 at 5:48 pm
This field would indicate which table that user's entries are in.
For more reasons than I could ever put in this tiny space, that would open a can of serious...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2008 at 1:13 pm
You don't need to go the route of XML... see the following...
http://www.sqlservercentral.com/articles/Test+Data/61572/
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2008 at 1:05 pm
Gotta be a little bit careful here... what Steve says is absolutely true... unless the WHERE clause is on a calculated or aggragated column in the SELECT list of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2008 at 1:03 pm
Ah... that would be a correct error because the index does not exist at compile time and SQL Server 2000 is gonna complain about it.
There's no need to name the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2008 at 11:50 am
Grant Fritchey (6/2/2008)
I find the percentage of the batch to be a pretty useful guide most of the time. Not all of the time, no, but more often than...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2008 at 11:34 am
I think the only thing that needs to change is changing TABLOCK to TABLOCKX...
Please post your latest error...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2008 at 11:29 am
Loner (6/2/2008)
Where do you live? There is no SQL Server job around your area ? Are you open to re-locate?
There are some... Most are filled and the rest...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2008 at 11:11 am
Loner (6/2/2008)
JeffEven you install SQL Server 2005 and learn it yourself, how do you put it on your resume because you don't have real life working experience?
I just direct them...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2008 at 7:58 am
Hi Scott...
You have some minor errors you need to fix... (found in 2k, and 2k5)
Msg 102, Level 15, State 1, Procedure fnc_AllowNumbersOnly, Line 8
Incorrect syntax near '?'.
Msg 102, Level 15,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2008 at 9:48 pm
Which version of SQL are you using? 2000, 2005, or ???
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2008 at 8:33 pm
Viewing 15 posts - 50,191 through 50,205 (of 59,091 total)