Viewing 15 posts - 53,356 through 53,370 (of 59,089 total)
If you setup a BCP format file correctly and use Bulk Insert, that problem will magically disappear... performance problems will probably disappear, as well. I've used Bulk Insert with...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 11:12 am
Thanks for the feedback, Jacob...
Yeah, the "same old trick" you're be speaking about is the aggragates themselves.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 11:06 am
Always a pleasure, MrPoleCat... and thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 11:04 am
Something had to have changed in the environment... for example, the login that SQL Server uses to start services... it may have been changed permission wise on the Windows Server...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 10:57 am
You haven't mentioned whether or not you're using an explicit transaction around all of those inserts and selects... that would be a real big cause of the deadlocks.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 10:55 am
You might want to take smaller bites when inserting, as well. Insert a couple of hundred thousand using a control (ugh!) loop.
If the data is being inserted from, say,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 10:49 am
Until they fix it, there's a work around...
1. Put your cursor one line above the code box.
2. Click and drag to one line below the code box.
3. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 10:46 am
Heh... understood... I still kick myself for some of the things I've done to a database in past lives 😀
Wouldn't really be an extra column and no tradeoff that I...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 10:42 am
I'd still be tempted to make the formatting in a calculated column for the app so I could easily create reports like "How many emails did we send today?". ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 10:01 am
My problem with a mega-watt satilite would be that some idiot would figure out a way to turn it into a beam weapon. ION drive? Way cool application...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 9:54 am
Always select just the columns that you need.
That goes without saying for the most part. But, again, I want to remind everyone that the OP said that Microsoft said...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 9:22 am
You bet...
Personally, what I'd rather see is a real DATETIME column and a CALCULATED column to provide the varchar version that the GUI needs. Somewhere down the line,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 9:20 am
JohnG (12/27/2007)
Use a return (OUTPUT) parameter as it is a much cleaner solution. You're calling a procedure and not a function. In coding, procedures are...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 9:13 am
Heh... dang it... I keep forgetting this is an SQL Server 2k5 forum! Thanks John.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 9:08 am
I saw that PIVOT is much faster than doing subqueries or CASE statements to transform aggregated data to columns
Jacob, if you have an example of that and a smattering of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 9:07 am
Viewing 15 posts - 53,356 through 53,370 (of 59,089 total)