Viewing 15 posts - 2,611 through 2,625 (of 22,227 total)
There's going to be work for data professionals for a VERY long time to come. That work will shift and change, as it already has. So yeah, it's a fine...
"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
April 26, 2019 at 1:31 pm
Can you post the rest of the code? If it says parameter has been defined, that means you're defining a parameter, but we can't see that in what you posted.
"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
April 26, 2019 at 1:27 pm
You can't.
You can use migration to replace it. You can use Azure Sync, but you have to set that up and program it. You can use something like Redgate Data...
"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
April 26, 2019 at 1:24 pm
Ignoring them might be valid. To check the wait statistics, run a query against sys.dm_os_wait_stats. That's in all versions of SQL Server from 2005 & up (although, Azure SQL 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
April 26, 2019 at 1:10 pm
I'd lean heavily towards this being overkill. Sure, queries on the one database don't interfere directly with the queries on the other. However, the resource contention is just as large...
"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
April 25, 2019 at 3:36 pm
It is. You can use UNION ALL and then run the same count against each view.
"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
April 25, 2019 at 3:33 pm
Easier question first, sure you can ignore the peaks... with the understanding that you'll see slow behavior, blocking, locking, and resource contention when you're trying to access memory & cpu...
"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
April 25, 2019 at 3:33 pm
If you want to understand why things are slow, get the execution plan and evaluate what is happening there. If you want us to help, share the execution plan. By...
"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
April 24, 2019 at 3:27 pm
Combining views, nesting views, and taking large, large data sets without filtering through views, are very common code smells that inevitably lead to trouble. Because views act like tables within...
"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
April 24, 2019 at 2:13 pm
Hard to explain exactly what happened, but it's likely to be the network. It's good to measure some queries from the client to understand how your network behaves, but 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
April 24, 2019 at 12:21 pm
I'm with Steve, Amazon or Azure blob storage. I lean pretty heavily towards Azure, but I nailed my flag to that mast a long time ago. Also, Steve has already...
"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
April 23, 2019 at 10:10 pm
PDW is parallel data warehouse. It's a huge appliance that your company paid a ton of money for. Read about it here. Polybase is a way to query other...
"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
April 22, 2019 at 1:32 pm
Well, for the one day loss, you can, if you want, leave the current backups in place.
As to the rest... woof! Huge task. I'll give you some things 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
April 22, 2019 at 1:26 pm
The single biggest issue you're going to hit on the database side of things is the new cardinality estimation engine that was introduced with SQL Server 2014. The new CE...
"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
April 22, 2019 at 1:16 pm
Impossible to even guess at this without seeing the full sets of code and the execution plans. Also, when measuring the speed, also measure the resource use, CPU and 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
April 22, 2019 at 1:12 pm
Viewing 15 posts - 2,611 through 2,625 (of 22,227 total)