Viewing 15 posts - 16,936 through 16,950 (of 22,226 total)
The overviews will barely get your feet wet. It's a hard thing to learn, or least I've found it to be so far.
"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
July 22, 2009 at 12:12 pm
Not a problem.
Another option, and it might not work for you, is to pass these values in a comma delimited format and then join against that single variable using 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
July 22, 2009 at 9:49 am
. (7/22/2009)
Steve, if you would prefer I didn't go forward 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
July 22, 2009 at 9:46 am
It could work, but you're going to run into a lot of issues, possibly. Do you have source control available? If not, get something like Microsoft's Team Foundation Server 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
July 22, 2009 at 9:44 am
Are there functions in the WHERE 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
July 22, 2009 at 9:39 am
If you want to view the cause of a lock, query sys.dm__tran_locks.
"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
July 22, 2009 at 9:36 am
BTW, This is a cross-post. I answered the same question over here:
http://www.sqlservercentral.com/Forums/Topic757335-145-1.aspx
Please don't post the same question in multiple locations. It really diffuses the conversation and duplicates effort.
"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
July 22, 2009 at 9:35 am
The one good source I know of is Allen White's blog. He's also published a couple of articles over at Simple Talk. If you find anything else good, let me...
"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
July 22, 2009 at 9:30 am
Yeah, estimated plans are seldom terribly helpful. It's basically the same plan though. It really looks like, based on what you provided, SQL Server is doing the right thing. An...
"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
July 22, 2009 at 9:18 am
That's a slightly odd looking plan. It doesn't have a SELECT statement or a query or any of the meta data about the plan in the XML. How did 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
July 22, 2009 at 8:38 am
Kit G (7/22/2009)
Grant Fritchey (7/22/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
July 22, 2009 at 8:00 am
Ah, right. ALZDBA answered it. You're not forcing the backup, you're forcing the restore, but not even that really, you're just kicking all the users off the database.
"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
July 22, 2009 at 7:24 am
Kit G (7/22/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
July 22, 2009 at 7:23 am
Tara (7/22/2009)
I think your point make sense to me but would like to know about how it works.
As you said we do have a column " Cdate " which is...
"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
July 22, 2009 at 7:20 am
You need to use the SQL Agent. It's right there in Management Studio. It runs as a service on the machine with SQL Server. Right click on the Jobs folder...
"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
July 22, 2009 at 6:17 am
Viewing 15 posts - 16,936 through 16,950 (of 22,226 total)