Viewing 15 posts - 7,141 through 7,155 (of 22,219 total)
That sounds like they're saying that they are already backing up the log, but if the log is that large, that might not be true (likely isn't).
It's pretty much...
"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 5, 2014 at 4:00 am
I'd put indexes on the table. The best choice, if you can only have a single index, would be a clustered index on the three columns in the WHERE clause.
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
December 4, 2014 at 2:45 pm
If you attempt to delete the file and it appears in any way to be locked, then it is in use even if you haven't identified by what yet. Don't...
"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 4, 2014 at 1:02 pm
Glad to hear you got the answer.
"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 4, 2014 at 12:03 pm
Everything I've done and heard suggests that 2014 is basically a more stable 2012 with many of the improvements of 2012 polished, including more stability in Availability Groups, better behavior...
"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 4, 2014 at 12:02 pm
curious_sqldba (12/4/2014)
My apologies, should have specified this. We already have a in-house alerting system, i just need 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
December 4, 2014 at 10:53 am
Using the GUI all the time with SQL Server 2014. It works just fine. Plenty of resources for learning it too.
"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 4, 2014 at 8:46 am
But now, it's just going to grow again. And while it grows, it's going to cause other processes to slow down and wait for that file growth. You're only temporarily...
"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 4, 2014 at 8:11 am
Not even a good guess. Now, frankly, I'm curious. I'm with Steve. Set this one fire and move on... after you capture the wait stats.
"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 4, 2014 at 7:57 am
I just remember, I wrote an article on just this topic[/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
December 4, 2014 at 7:48 am
yeah, if you want to explore multi-server management, you certainly can schedule them to run across multiple servers.
"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 4, 2014 at 7:46 am
Weird.
I tried to replicate it. Standard worked just as fast as Enterprise on the VM I created.
Have you tried capturing wait stats before and after running the create database command?
"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 4, 2014 at 7:18 am
Yeah. It'll generate a script, or you can generate a report of the differences, or both. All from the command line. I forget the syntax, but it's in the documentation.
"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 4, 2014 at 5:02 am
OK. I'm back.
I spun up an Enterprise server taking all the defaults and then created a database. It only took about 3 seconds (if that). Maybe this is on Standard?...
"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 4, 2014 at 4:46 am
And because you're selecting everything, that's all stored with the clustered index, hence the scan.
How many rows is it returning out of how many rows in 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
December 4, 2014 at 4:17 am
Viewing 15 posts - 7,141 through 7,155 (of 22,219 total)