Viewing 15 posts - 8,701 through 8,715 (of 22,226 total)
Try modifying the system database called model to have the security settings you want as outlined above. Then, when you create a new database, what's in model is what gets...
"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 12, 2014 at 4:50 pm
Well, thinking about it some more, you can turn on auditing on the blob stores where the VM files are located. Set that to verbose and see what the heck...
"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 12, 2014 at 4:48 pm
No, statistics aren't modified by backups.
I've been using SQL Server on Azure in VMs a ton. I haven't seen this problem crop up before, so I'm seriously stumped on what...
"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 12, 2014 at 4:46 pm
No argument, but usually, it's relatively rare to change primary keys once a system has been built. It certainly doesn't make the early design and build stages or 1.1 releases...
"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 12, 2014 at 9:13 am
But a cost of 5 is so cheap that plans that shouldn't be parallel can get set up as parallel, running longer and using more resources than they should.
"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 12, 2014 at 7:06 am
GilaMonster (3/12/2014)
Am I slow today, or was this a little tricky to figure out? http://www.sqlservercentral.com/Forums/Topic1550137-1292-1.aspx
No, that one was weird.
"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 12, 2014 at 6:40 am
Do you have database backups? You'll need to go to those to restore your system.
"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 12, 2014 at 3:28 am
Based on what you're showing, those two queries are identical. There are so few tables the optimizer is going to rearrange the order to suit itself any way. There's no...
"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 12, 2014 at 3:26 am
Editing and rewriting the query tuning book for 2014 when I came across this:
Queries may be attempting to deal with data in a row-by-row fashion (or to quote Jeff Moden,...
"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 11, 2014 at 5:45 pm
If the memory is available to the OS, SQL Server can also use it.
As for changing from 0 to 4, 0, the default, uses all processors available. You don't need...
"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 11, 2014 at 5:27 pm
Maybe get them a copy of Craig Mullins book, Database Administration. It's an awesome overview of the job. It doesn't get into technologies directly, just responsibilities and concepts. I realize...
"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 11, 2014 at 5:25 pm
First blush, no, I wouldn't say it's a "bad" design.
But, if I see varchar as a primary key, I'm assuming natural keys. There are good reasons for this from both...
"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 11, 2014 at 5:22 pm
MyDoggieJessie (3/11/2014)
+1 Grant, that's where I was heading with my thoughts but very hard to guess at it without any example of the code used :hehe:
I see function... the rest...
"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 11, 2014 at 4:13 pm
If it's multi-statement table valued functions, it's because they're notorious for bad behavior and poor performance.
"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 11, 2014 at 12:16 pm
Let's also be careful about parallelism. It's a good thing. It's just that some queries are set as parallel that shouldn't be. Adjusting the cost threshold for parallelism up from...
"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 11, 2014 at 12:05 pm
Viewing 15 posts - 8,701 through 8,715 (of 22,226 total)