Viewing 15 posts - 11,461 through 11,475 (of 22,219 total)
YEah 1gb is going to be very hard to work with. However, creating a table, dropping a table, these operations should be fairly quick. You're probably just hitting resource contention....
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 5, 2012 at 1:08 pm
If the size is less than 8 pages, it's going to be stored on mixed extents and defragging is going to be an utter waste of time. You might even...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 5, 2012 at 1:05 pm
Just one point worth considering, how much are the differen applications dependent on the data from each other. If it's fairly light, splitting up allows you to have multiple indepdendent...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 5, 2012 at 1:04 pm
CELKO (1/5/2012)
My book SQL PROGRAMMING STYLE...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 5, 2012 at 12:32 pm
Just a note, the use of no_lock CAN reduce time because it reduces locking, but it's not an automatic. Not trying to get into the whole no_lock discussion, but we...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 5, 2012 at 9:01 am
Yeah, I can't spot any differences either. Hmmm.... Estimates & actuals are off, more than a little bit. I know you updated the statistics, but did you try using WITH...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 5, 2012 at 7:03 am
Take a look at the sys.dm_exec_query_stats DMO. You should be able to get a count from that assuming the statement is still in cache.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 5, 2012 at 6:41 am
It does 1/3 the number of reads, but increases the time? No, that's not one I've seen. Can you post both actual execution plans? I know you say they're identical,...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 5, 2012 at 5:06 am
I've never seen a hard & fast ruling on this one. I generally go between 1/10 and 1/5 of the size of the database and then watch things from there....
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 5, 2012 at 4:24 am
Koen Verbeeck (1/4/2012)
Did I miss anything...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2012 at 1:53 pm
I would say no, Microsoft doesn't have a simple list of coding standards. But, if you want some Microsoft endorsed list of best practices, I'd check out the Static Code...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2012 at 11:35 am
If you have different ANSI settings on the connections, you'll have different plans. If you're calling the query one way from the app (parameterized query, stored proc) and a different...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2012 at 10:03 am
Marco V (1/4/2012)
to run through the data it goes between 20 and 30 seconds (maxdop 1 is going abit faster).
i also...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2012 at 8:43 am
I would not suggest installing SQL Server if you're going to be changing the server name, etc. Get the server set up and configured, then install SQL Server. You'll have...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2012 at 5:44 am
What about just using the query window and typing 'UPDATE dbo.MyTable SET ColumnA = 42 WHERE ColumnB = 42'?
The gui in SSMS can support what you're doing, but it's a...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2012 at 5:43 am
Viewing 15 posts - 11,461 through 11,475 (of 22,219 total)