Viewing 15 posts - 19,126 through 19,140 (of 22,219 total)
Jeffrey Williams (12/9/2008)
Grant, I would not recommend issuing the above - especially since it is deprecated in SQL Server 2008. Here is the message you will get on 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
December 9, 2008 at 12:51 pm
First things first, I think your statistics may be out of date. on [SWUS].[dbo].[SW_Ord_List_Ext].[_dta_index_SW_Ord_List_Ext_23_254064091__K3_1_4_5_18_20_22] [OLE]. The estimated number of rows is 54, the actual is 48000. That's a bit of...
"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
December 9, 2008 at 11:49 am
Not surprising. The function is basically running a query for each and every row in your database.
A better approach would be to JOIN to the lookup table, either directly or...
"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
December 9, 2008 at 11:39 am
In general, yes, you'll want to have multiple file groups. I'd recommend them for your OLTP system too. As to specifcally how many and where, that's hard to to say....
"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
December 9, 2008 at 11:03 am
Instead of shrinking the database at the beginning of the process, I'd suggest growing the log out to the necessary size and making sure that it's cleaned out (BACKUP LOG...
"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
December 9, 2008 at 10:55 am
Do you have an execution plan showing how the function is behaving?
"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
December 9, 2008 at 10:53 am
That's great. I hadn't even tried it in 2005. Thanks for posting.
"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
December 9, 2008 at 10:51 am
Total agreement.
"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
December 9, 2008 at 7:57 am
OUTPUT parameters will do the trick, but they'll only work for single row inserts. If you need to do any batch work, you'll want to look into the OUTPUT clause...
"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
December 9, 2008 at 7:54 am
Yes, I want direct control over what is run and how it is run within my system. Maintenance jobs are OK, but they can be problematic. I have a lot...
"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
December 9, 2008 at 7:51 am
check the collation settings between each database, the connection settings (with focus on ANSI settings) and, check the service packs and hot fixes to ensure they're both the same.
"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
December 9, 2008 at 6:47 am
dastagirid (12/9/2008)
I WANT TO KNOW WHAT IS THE LAST 10 RECORDS IN MY DATABASE TABLES .IS ANY COMMAND IS THERE OR NOT ? ...
You have to ask the last...
"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
December 9, 2008 at 6:44 am
Is that 11 million on top of the 12 million? You could be looking at more and page splits and index reorgs on top of the stuff that Jack mentioned.
"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
December 8, 2008 at 9:49 am
Something is shutting down your database. If it's not AUTO_CLOSE, it's something else. Code sure seems like the next best bet.
"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
December 8, 2008 at 8:10 am
Is it possible the database is being closed by the app when it closes it's connection? That's possible.
"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
December 8, 2008 at 8:03 am
Viewing 15 posts - 19,126 through 19,140 (of 22,219 total)