Viewing 15 posts - 46,711 through 46,725 (of 59,095 total)
Jeffrey Williams (12/7/2008)
Instead of trying to fiddle with IGNORE_DUP_KEYS on the index, ...
No "fiddling" required... it's set it and forget it. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2008 at 10:35 pm
... heh... or some very high velocity pork chops fired at point blank range. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2008 at 10:31 pm
That method using insert/rollback is a great place for more RBAR to occur... and it takes twice as long... 1 period for an insert... 1 period for a rollback... and...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2008 at 10:27 pm
Heh... I say, stop messing with it. Sample the size of the used portion for a month, use that determine the growth rate for 12 months, set it to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2008 at 9:46 pm
I just copy directly from prod to archive... no staging. I do it in small enough chunks where I don't need a cursor to prevent blocking.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2008 at 8:05 pm
If you really want to lock things down, use BULK INSERT and format files (if you need them). Take a peek in Books Online.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2008 at 7:43 pm
Run DBCC UPDATEUSAGE and see if that get's rid of the negative numbers.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2008 at 7:36 pm
Worked for me.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2008 at 7:33 pm
Heh... it's the twiching eye that really gets to them. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2008 at 6:03 pm
BWAAA-HAAAA-HAAA! OMG!!! ... If you think the posted questions are getting worse, you aint seen nothin' compared to real life... here's some code I just found in one of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2008 at 12:56 pm
If the [Field Length] isn't character based (and, it shouldn't be), you'll probably have to add an explicit conversion to [Field Length]... but it is the classic way to do...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2008 at 5:11 am
Absolutely agree... but it won't change their mind...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2008 at 4:57 am
30 seconds for only 4K records? Take a look at the following...
http://www.sqlservercentral.com/articles/Test+Data/61572/
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2008 at 8:32 pm
mm... I'm confused... you say the time format is "tttt", but you have six characters for the time in both examples and one of the sets of 6 looks like......
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2008 at 8:23 pm
Or, you could do a cross-tab...
http://www.sqlservercentral.com/articles/T-SQL/63681/
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2008 at 8:08 pm
Viewing 15 posts - 46,711 through 46,725 (of 59,095 total)