Viewing 15 posts - 54,181 through 54,195 (of 59,072 total)
Just a different slant on things...
-- DROP TABLE #T
GO
--===== Create a table to store the results in
CREATE TABLE #T
(
...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2007 at 10:40 pm
And, please don't post duplicate posts.... we'll find ya...
http://www.sqlservercentral.com/Forums/Topic420902-145-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2007 at 10:09 pm
Duplicate post...
http://www.sqlservercentral.com/Forums/Topic420896-146-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2007 at 10:07 pm
Lordy, I hate setting up test data for payroll examples... whatever...
Here's some code that generates 100,000 entries for 200 employes for a year's worth of payroll following your rules...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2007 at 9:30 pm
So, double check one more time...
All indexes (indluding primary keys) on the test box are also available on the production box.
All tables have the same row count on both boxes.
All...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2007 at 5:29 pm
You didn't listen to me... lookup "expanding hierarchies" in Books Online and adapt it. It WILL do as you ask.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2007 at 5:18 pm
Oh, little nuances like will there ever be more than 2 names in a class? If so, do all the scores have to be the same or just 2?...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2007 at 9:16 am
Yes, there's an easy way to do the whole thing... without a loop. The loop is just going to make this very slow...
Recommend you post your code and let's...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2007 at 6:55 am
And, to be sure, it DOES matter where you put the filters in the case of an OUTER JOIN.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2007 at 6:52 am
I think you're gonna need to be a bit more specific in your question... I for one, have no idea what your question is actually about.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2007 at 6:31 am
Activity counts, basically...
Something like 1 point per post, 1 or 2 points per script (not sure there), etc.
Notice that these are also migrated from the "old" format of the forum...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2007 at 6:29 am
I don't think so, but links are sometimes a bit picky. If you don't find any other problem, I think I'd set up a small test to make sure.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2007 at 5:44 am
Add an IDENTITY column to the table with the correct seed...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2007 at 12:15 pm
Heh... yeah, agreed... I've seen folks destroy production with an UPDATE as well... but it was never with the proper form of update (like Greg's is) which must be "If...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2007 at 8:22 am
Bob Fazio (11/2/2007)
I forgot to add.If you have several queries (which most people do) create an index based upon the more common set of those fields.
What...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2007 at 8:01 am
Viewing 15 posts - 54,181 through 54,195 (of 59,072 total)