Viewing 15 posts - 8,581 through 8,595 (of 22,224 total)
Are there differences between the cost threshold for parallelism between the two? How about optimize for ad hoc? Are there differences in the amount of memory or CPU? When 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
March 24, 2014 at 11:28 am
Without seeing the indexes, I can't even guess at what to do.
"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 24, 2014 at 11:25 am
A seek is dependent on the WHERE clause being able to use the statistics that define the data stored on the index. Not seeing your query, I can't make suggestions...
"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 24, 2014 at 11:23 am
I'd suggest using extended events. You can capture the recompiles and you can filter the event so you're only capturing information for the query or stored procedure in question. It's...
"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 24, 2014 at 6:54 am
Backing up across a network like that can be slow. A better approach is to backup locally and then copy the backup over. That way, the copy process can run...
"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 24, 2014 at 5:13 am
Solid State Drive.
It's a drive that uses memory like it was a spinning platter hard drive. So, it's just a drive. SQL Server uses it like any other drive. Just...
"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 24, 2014 at 5:02 am
That looks like hardware as a bottleneck. It's the writes that are going slow.
"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 24, 2014 at 4:49 am
I'm pretty sure you posted this in the right spot. Although you could go to the Employers and Employees forum or maybe Resumes and Job Hunters. But I'd think you'll...
"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 23, 2014 at 4:27 am
But now you have that $lastwritetime construct in there. That's what's giving you conniptions. Check the documentation on test-path again. There isn't a date filter that you seem to be...
"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 23, 2014 at 3:06 am
Pretty sure it's this bit
Test-Path -Path "\jfocus01\WFMASTERS\Created\$file3*.tab" -eq (get-date)
-eq isn't a parameter for Test-Path.
"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 22, 2014 at 5:02 am
I'd suggest going to the logs to read what they have to say about 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
March 22, 2014 at 4:53 am
You'd need to run the restore... which is probably going to take quite a while. 96gb is a reasonably large number of open transactions.
"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 22, 2014 at 4:52 am
Perry, really? I've seen more issues with CPU and memory from VMs since those are the shared resources. Not arguing, just requesting more information.
"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 21, 2014 at 9:39 pm
The core concepts of relational data storage and database administration are the same. So tons and tons of your knowledge is going to transfer pretty easily. But, the devil 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
March 21, 2014 at 4:20 pm
suneel kamavaram (3/21/2014)
It needs a covering index.See here[/url] and BOL
Thanks for bringing up the book. For execution plans though, I'd recommend this one....
"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 21, 2014 at 4:17 pm
Viewing 15 posts - 8,581 through 8,595 (of 22,224 total)