Viewing 15 posts - 53,461 through 53,475 (of 59,098 total)
Yes, there is a "secret"... simply think about what you want to do to columns instead of what you want to do to rows. That and having a little...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 9:20 pm
Now, thats a "hint" if I ever saw one... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 8:26 pm
Jason Selburg (12/21/2007)
No problem Jeff! I'm really starting to se the true value of the Tally table BTW.. 😀Hey, you never answered my PM.
Heh... another compliment. Thanks, Jason, but...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 8:16 pm
(Good to see you're starting to like some of the new tricks out there Jeff!)
Shoot... once I learned it, I was just aching for a place to use it! ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 8:11 pm
Troy Doherty (12/21/2007)
By deleting records < select @dt = datediff( d, -94, getdate()) i would have deleted all of my data.....:w00t:
Heh... Troy, you must have a death wish... testing deletes...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 8:01 pm
That's quite a compliment, Jason. Thanks. Glad to see someone take it to the next level by actually getting a better job from what they're learned by looking...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 6:11 pm
Unless the "spaces" between the columns are something besides spaces, then you can't use BCP to import this file because the country names may also have spaces.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 6:08 pm
The best answer for SQL Server 2000 is, in fact, the Temp Table solution. It's nasty fast, especially if you use a SELECT/INTO.
The solution that Absinthe showed ...
select (select...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 6:04 pm
The seed should probably the value returned from the NextID proc...
Other problem is, you have to increment the NextID in the NextIDtable by the number of rows you have in...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 1:15 pm
Think of it as a "going away present", Jason. Good luck on your new job!
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 1:06 pm
There's no need to convert to a number and then back to a date if the data is just being used in a WHERE clause... for example... a modification of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 1:03 pm
What is the primary key of the table? Please include the datatype...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 12:46 pm
In terms of the original script, I unfortunately haven't noticed any significant difference worth writing home about in terms of execution time after changing it from a cursor to a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 12:41 pm
The problem is that you never give the system time to "breath"... sure, it only takes about 3 seconds to delete 100,000 rows provided you don't have Delete Triggers on...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 11:35 am
Adam Angelini (12/20/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 11:10 am
Viewing 15 posts - 53,461 through 53,475 (of 59,098 total)