Viewing 15 posts - 54,826 through 54,840 (of 59,072 total)
One of the recommendations in Books Online under "deadlocks, avoiding" is...
Keep Transactions Short and in One Batch
A deadlock typically occurs when several long-running transactions execute concurrently in the same database....
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 7:37 am
And, lookup "parameter sniffing" on this site or Google...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 7:33 am
Like everything else, it depends...
It's easier to maintain security differences on two procs if you only want certain people to be able to use the "full-details" version. If you...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 6:15 am
I agree with Ed... sure, you should be sending backup tapes off site. Sure, you should save some text files and send them offsite. And, I agree... what...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 6:03 am
Adding an Identity column to each table isn't that much work if you write a little dynamic SQL to do it for you... especially if you have it all worked...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 5:56 am
Heh... thanks, Lowell... you're too kind :blush:
Clarence,
If your barcodes/customer numbers get above 11,000, you can very easily change the "Tally" table to a million, but I wouldn't go much higher...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 12:22 am
It's an SQL Server 2000 forum... no CTE's here...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 12:16 am
Hi Mick,
Long time, no see...
Just an FYI... be real careful about using SET ROWCOUNT... if the queries after the SET have ORDER BY on large tables, you're going to...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 12:13 am
...or duplicated data...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 12:03 am
Doesn't matter if it's varchar or not... your method still works...
declare @i decimal(10,2)
Set @i = 1078.734
PRINT REPLACE(@i,'.','')
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2007 at 12:02 am
Already did... look at my previous post... the one where I tell you to just lock the table. Also, Remi asked how many total rows are in the table......
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 11:53 pm
Yeah, I know it's not "monitoring"... but, when you figure out that the hardware is doing it's very best and you're still having performance problems...
Step 1... search code for cursors
Step...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 10:31 pm
Cherie,
Just a tip in case you didn't know... if you get such an error in Query Analyzer (message window), the first thing you should probably do is to double click...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 10:19 pm
Heard you can get paid for drinking beer 😉 Still looking for that one 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 10:14 pm
Yeah, huh? Can you feel the love there? :laugh:
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2007 at 10:13 pm
Viewing 15 posts - 54,826 through 54,840 (of 59,072 total)