Viewing 15 posts - 17,851 through 17,865 (of 22,226 total)
That is really interesting. The plans themselves are almost identical, but the coaelesce is reducing the amount of data being accessed. Instead of 600 million rows, it's only 8 million....
"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
March 31, 2009 at 11:50 am
Ken McKelvey (3/31/2009)
"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
March 31, 2009 at 11:44 am
Jack Corbett (3/31/2009)
I'm reading it as 600 million rows (627,966,462) from the Full Text Engine.
I'd also be interested in the execution plan from the Coalesce function query.
You might 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
March 31, 2009 at 8:18 am
to rebuild or reorg is a kind of a hard decision. You can apply a rule and see how it works and adjust to meet your needs. Say 30% to...
"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
March 31, 2009 at 8:09 am
james.spibey (3/31/2009)
Can you post the actual execution plan? Just save it as a .sqlplan file, zip it and attach it.
I see that your TVF is also calling another function. Just...
"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
March 31, 2009 at 8:04 am
Yeah, that's exactly what I was thinking. It would prevent the use of the index. That's a concern usually, not a goal. That's why I'm a bit confused.
"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
March 31, 2009 at 7:52 am
I've never heard about using COALESCE as a tuning mechanism before. What do you do with it and how do you format it? Is there a set of tests you...
"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
March 31, 2009 at 7:45 am
I'm pretty sure you can't limit the forwarding, but I'm pretty sure you can limit the number of alerts or emails that are sent from the email enabled sql server....
"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
March 31, 2009 at 6:26 am
So from the sound of it, you have dbcreator rights, but not securityadmin. Without at least that, you can't restore a database and give permissions to access it.
"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
March 31, 2009 at 6:09 am
Can you post the actual execution plan? Just save it as a .sqlplan file, zip it and attach it.
I see that your TVF is also calling another function. Just so...
"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
March 31, 2009 at 5:46 am
But even then, you can only add users if you have the security admin privileges to do that.
"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
March 31, 2009 at 5:41 am
You don't need error handling or transactions for the SELECT part of the query. There's nothing going on there that requires it.
As to the rest, here's an article I wrote...
"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
March 31, 2009 at 5:13 am
You can't. That's a hard limit built into the system. That's a lot of data to be sorting on. Do you have any options there? What are you trying to...
"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
March 31, 2009 at 5:06 am
If it's eliminating NULL values you might see an increase in performance, but I'm not sure. Can you post the execution plans along with the queries?
"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
March 31, 2009 at 5:04 am
If you're the admin on the server you should be able to connect to it. What specifically is the error message.
If you have security admin privileges on the server, you...
"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
March 31, 2009 at 5:02 am
Viewing 15 posts - 17,851 through 17,865 (of 22,226 total)