Viewing 15 posts - 51,211 through 51,225 (of 59,098 total)
Shouldn't be a problem... I import 4 million CDR's at a time...
You haven't given us much to work on... What are you using to do the import? And, would...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2008 at 7:00 am
The only time WAIT FOR blocks anything is when it's inside a transaction (it doesn't block, it causes the blocks to stay open longer). Of course, it keeps a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2008 at 6:46 am
Meghna,
Just curious... why do you need to do such a thing?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2008 at 6:43 am
Heh... I don't think anything is guaranteed across versions, ST... but the same number is returned in both SQL Server 2000 and 2005 when I run your sample code of...
select...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2008 at 6:33 am
Thanks... I've not experienced that in 2k... mostly because I won't let my guys use WHERE IN... Haven't seen a bad plan for WHERE NOT IN yet, either, but that's...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2008 at 1:19 am
Matt Miller (4/8/2008)
one of these days - I'm going to figure out how to colorize my code without turning it into a wreck........hehe
:hehe: How'z 'bout taday 😛
http://extras.sqlservercentral.com/prettifier/prettifier.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2008 at 12:17 am
Matt Miller (4/8/2008)
Jacob - you hit it on the nose. Forcing the join hint makes the difference.
Crud... SQL Server is getting more like Oracle every day 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2008 at 12:15 am
Bob...
Don't need the join at all if only the Attendance table is involved and the join has nothing to do with getting rid of the Temp table. Were inserting...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2008 at 9:06 pm
Wow... lemme say that again... WOW! SQL Server 2005 sucks for this! Yeah... it was a real world example.... In the real world, we have SQL Server...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2008 at 8:57 pm
Matt Miller (4/8/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2008 at 8:05 pm
If you're going to do it that way, Bob, you need to understand that you may have a fundamental flaw in your code... remember the comment in one of your...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2008 at 7:08 pm
Heh... you should compare those with STUFF 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2008 at 6:07 pm
There's a bunch of "sys.All_" views that are "server wide".
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2008 at 6:05 pm
Thanks for the feedback folks. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2008 at 6:00 pm
Sure, you could sub RowNum for *... not sure it matters for performance here as it might in other places. * allows it to pick the best index it...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2008 at 6:30 am
Viewing 15 posts - 51,211 through 51,225 (of 59,098 total)