Viewing 15 posts - 7,396 through 7,410 (of 22,219 total)
You're not simply nesting the functions, you're self-referencing. That's very different, and, as you're seeing in the error message, not allowed.
"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
October 10, 2014 at 6:22 am
ERStudio by Embarcadero is one of my favorites.
"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
October 10, 2014 at 6:09 am
No. You can't.
The language for manipulating SQL Server is T-SQL. Not HTML. That stands for Hyper Text Markup Language. Transaction Structured Query Language is for SQL Server. They are not...
"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
October 10, 2014 at 6:09 am
I'd suggest looking at a few more pieces of information. What are your wait statistics like. And, check this article for a few more[/url]. Note, the query that shows 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
October 10, 2014 at 6:07 am
The domain account that Agent is running in will need to have permissions set for 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
October 10, 2014 at 6:02 am
Best suggestion, you take it a step at a time. Be structural in your approach. Understand what's happening and why, then make adjustments to change the behaviors you don't like....
"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
October 10, 2014 at 5:03 am
Totally wild stab in the dark, but what's the fill factor on the index?
"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
October 9, 2014 at 3:46 pm
santoshkal (10/9/2014)
when i run the query it always taking non clustered index scan on execution plan...
"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
October 9, 2014 at 8:18 am
It's hard to argue with that. If you don't need it, don't create it.
The key point is that the execution plan for a batch is created all at once. 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
October 9, 2014 at 6:27 am
santoshkal (10/9/2014)
after using where clause also its taking 100% cost ?any other way to improve ?
thanks
That's a measure of an estimate in comparison to measures of other estimates. 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
October 9, 2014 at 6:24 am
sqldriver (10/9/2014)
Grant Fritchey (10/9/2014)
"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
October 9, 2014 at 6:21 am
I wouldn't suggest passing the value as a string. You're potentially taking away the ability of the optimizer to use parameter sniffing (a good thing the majority of the time)...
"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
October 9, 2014 at 5:52 am
Just so we're clear, those really are two very different queries. One references a single table. The other references two tables.
I agree with the other comments, but I think...
"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
October 9, 2014 at 5:50 am
You can get a determination of the performance and usefulness of an index three ways. First, you measure the time on a given query before and after applying the index....
"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
October 9, 2014 at 5:48 am
I like Eddies rules. The one thing I would add is that, unlike 2000, in 2005 and up, you're going to see statement level recompiles, not procedure level recompiles (unless...
"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
October 9, 2014 at 3:40 am
Viewing 15 posts - 7,396 through 7,410 (of 22,219 total)