Viewing 15 posts - 8,581 through 8,595 (of 22,219 total)
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
milos.radivojevic (3/21/2014)
"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:14 pm
In general a key lookup means that the index used didn't have all the columns available so it had to go to the clustered index to get those missing columns....
"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:12 pm
Yeah, I'm with Luis. Most tables should have clustered indexes. Since it stores the data, it should generally be the primary path to the data. That's not necessarily the primary...
"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:08 pm
Availability Groups are a mechanism for setting up the ability to fail a database or a set of databases from one server to another. With this setup, there is nothing...
"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:07 pm
You can run Hadoop on Windows just fine. I've done it. Micrososft does have a port of it available in Azure called HDInsight. Here's a link to check it out[/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
March 21, 2014 at 4:03 pm
Viewing 15 posts - 8,581 through 8,595 (of 22,219 total)