Viewing 15 posts - 16,426 through 16,440 (of 22,229 total)
If the users are correctly matched to the logins... I still fall back on the backup is different than you think it is. Assuming the users are correctly in place...
"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
September 30, 2009 at 6:59 pm
You must be using an out of date backup. I've seen users missing on a restore because the login doesn't exist from one server to another or the login &...
"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
September 30, 2009 at 11:55 am
john.arnott (9/29/2009)
Am tempted to reply to the non-question with just:42
But that may be too obscure.
I almost posted that as a response but I thought it might tend to start 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
September 30, 2009 at 5:29 am
bmw110001 (9/29/2009)
it's a live application the query fetches info from other srvr's the thing i got it's a query which is in loop,any idea
Eliminate the loop?
"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
September 29, 2009 at 1:26 pm
bmw110001 (9/29/2009)
hi Grant FritcheyHave done everthing to solve the issue even moved db from 2005 to 2008 but still the issue persists
Then I guess the core question is, what's the...
"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
September 29, 2009 at 9:00 am
You can simply put the statement RETURN in the IF statement like this:
IF (@a = 0) AND (@b = 0)
BEGIN
RETURN
END
ELSE
BEGIN
SELECT....
END
But, you'd be better off returning a value of some sort,...
"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
September 28, 2009 at 7:25 am
I'm going to pile on a bit and agree with Jeff. When you have views calling views that are joined to views, you will begin to get very poor execution...
"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
September 28, 2009 at 7:16 am
There's no real way to limit access of a given database to memory or cpu on the server. If you have a badly performing database, you'll need to isolate 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
September 28, 2009 at 7:12 am
You need to also pass in the owning schema of the table as @table_owner.
"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
September 28, 2009 at 7:04 am
I'm afraid I don't understand the question. Can you expand on it a bit?
"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
September 28, 2009 at 6:54 am
Use the TRY/CATCH construct. It provides the most power for what you need. There's an introductory article here[/url].
"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
September 28, 2009 at 6:51 am
Just for curiousity, what did you do to solve the performance issue?
I see a function on a column in the WHERE clause that will prevent index use. Was that 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
September 28, 2009 at 6:48 am
None that I'm immediately aware of. I'd have to do a search 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
September 27, 2009 at 5:18 am
jcrawf02 (9/25/2009)
Grant Fritchey
You going to the summit?
I got this picture in my head of Grant in mountaineering gear on the slopes of Everest as he passes Alvin...
And there's...
"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
September 25, 2009 at 1:24 pm
Roy Ernest (9/25/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
September 25, 2009 at 1:22 pm
Viewing 15 posts - 16,426 through 16,440 (of 22,229 total)