Viewing 15 posts - 50,206 through 50,220 (of 59,102 total)
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
Any chance of changing the design to something a bit more normal instead of storing seconds for hours, minutes, and seconds?
Also, what have you tried? Generally speaking, you should...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2008 at 8:23 pm
Spend %50-60 USD on SQL Server 2005 Developers edition... install it on your home PC. Start answering/verifying questions on this forum... you'll stay current.
But it does takes some...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2008 at 5:08 pm
Um... is [DC-Base] the changing part number you're referring to? And, if so, what is the datatype of that column?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2008 at 4:56 pm
Ronnie.Doggart (6/1/2008)
HiWhen you say I/O output problem do you mean network bandwidth ?
Ronnie
Yep... that and recompiles... because of the 1=1 trick to make it easier to form a WHERE clause,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2008 at 10:26 am
Viewing 15 posts - 50,206 through 50,220 (of 59,102 total)