Viewing 15 posts - 9,196 through 9,210 (of 22,219 total)
Seems OK to me. I'm not crazy about the pattern where you name each PK with the same name and then you have to figure out where it's used elsewhere....
"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 20, 2013 at 4:17 am
Grab a copy of my book down in my signature. It tells you all about tuning your 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
December 20, 2013 at 4:10 am
This really sounds like a job interview. If so, you ought to be able to 1) Answer these questions for yourself 2) Look them up through Google or Bing 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 20, 2013 at 4:09 am
Sean Lange (12/19/2013)
Koen Verbeeck (12/19/2013)
GilaMonster (12/19/2013)
https://www.surveymonkey.com/s/TribalAwardsVoting
😀 :hehe:...
"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 19, 2013 at 5:33 pm
That is odd. Any chance those databases are set to auto_close? If so, they won't have performance counter metrics.
"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 19, 2013 at 5:16 pm
According to the Microsoft documentation, that's it. Did you run the install? If it installed without error, follow the instructions on this page to fire it up.
"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 19, 2013 at 1:03 pm
Which rows are missing?
"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 19, 2013 at 1:00 pm
Of course you are right and I'm sure you understand these concepts inside and out. But the OP sounded to me like a complete beginner and your rigorous analysis...
"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 19, 2013 at 12:24 pm
If the user is able to execute the procedure without error, then that user has access to the stored procedure. Maybe the security is internal and just preventing the delete...
"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 19, 2013 at 12:14 pm
Wait, define "during time period of query"
SQL Server suggests that it supports nested commits, but it doesn't really. If you have a transaction and it had three transactions inside 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
December 19, 2013 at 12:12 pm
As long as development is in source control, I wouldn't sweat it much. I had nightly backups running on dev (along with source control) just because it made it faster...
"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 19, 2013 at 12:11 pm
Some of the WMI errors are due to security settings. Check this web page for details.
"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 19, 2013 at 12:04 pm
It'll do the basics, but don't be shocked if some of the GUI stuff completely wipes out, like, backups, due to the changes there, will likely crash. I don't know...
"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 19, 2013 at 11:59 am
Sounds like a good plan. If you hit snags, you know where to go.
"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 19, 2013 at 11:56 am
What Gail said. Likely you saw a spike or several spikes from index rebuilds. Regardless, the choices are, log backups, or simple recovery. Anything else just inflicts pain, and who...
"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 19, 2013 at 11:36 am
Viewing 15 posts - 9,196 through 9,210 (of 22,219 total)