Viewing 15 posts - 9,211 through 9,225 (of 22,219 total)
If you still want point in time recovery, then add a second maintenance routine that runs... I don't know, once an hour (seems like you don't have many transactions) that...
"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 8:38 am
You can't create a view to a "dynamic source." You have to be able define a specific table or set of tables for a view. I'm not sure what 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
December 19, 2013 at 8:05 am
Since you're not doing anything with the log backups anyway, take the database out of full recovery. Just use Simple. That won't eliminate all log problems forever, but it'll certainly...
"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 8:02 am
This is why I still like standard discussion style forums as opposed to Question/Answer forums like StackOverflow. Yeah, if you have a very clear and specific question and want 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
December 19, 2013 at 6:54 am
You have a very clear error:
The system cannot find the path specified
It has to be something related to this issue.
"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:46 am
Read the description of a seek. It's basically the same as a scan. But in this case, it thinks it can seek a limited range but ends up seeking on...
"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 3:59 am
Take a look at extended events. You can capture the login event and then add the nt_username global field. There's also a session_nt_username as well as a username global field....
"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 3:51 am
There's a nice introduction to it[/url] over on Simple Talk.
SQL Server 2014 has updateable columnstore indexes.
"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 18, 2013 at 4:33 pm
None of those is anything to do with a server's overall health. SQL Server doesn't really have such a thing built in. But, the closest you can get to 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 18, 2013 at 4:30 pm
Elliott Whitlow (12/18/2013)
I would suggest looking here for your answers: http://technet.microsoft.com/en-us/library/ff878487.aspxCEWII
Yay! Books Online!
"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 18, 2013 at 3:45 pm
I could, but won't, argue that identities are a crutch. Natural keys can work fine. I try not to worry too much about the key structure while I get things...
"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 18, 2013 at 3:28 pm
The system_health extended events session that runs by default captures deadlocks. You can see the full deadlock graph there.
"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 18, 2013 at 12:40 pm
OK. That was just 2014 acting cute. I did get two different plans in 2012.
To understand the differences, look to the properties. I have both plans using an Index...
"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 18, 2013 at 12:39 pm
Unfortunately, I just tested it on my machine and got identical execution plans for the two queries, which is what I expected. I'm going to go and try a couple...
"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 18, 2013 at 12:27 pm
So that still breaks down the same way. A class will have a relationship with multiple students. And a student will have a relationship with multiple classes. So, the way...
"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 18, 2013 at 11:51 am
Viewing 15 posts - 9,211 through 9,225 (of 22,219 total)