Viewing 15 posts - 2,596 through 2,610 (of 22,219 total)
Sounds like you're not logging in correctly to Azure then. You can only use Azure Active Directory, not the regular kind, or, a SQL login, which you say you 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
May 7, 2019 at 12:00 pm
Connections should be exactly the same. What's the error?
"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
May 7, 2019 at 11:31 am
Also, look up Ola Hollengren's scripts for backups. They'll serve you well.
"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
May 7, 2019 at 11:08 am
Have you ever encountered some code that makes you feel that you need wine instead of coffee to fix it? Or is it just me? I'm working on 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
May 3, 2019 at 5:35 am
Since you're not at liberty to share the queries - the only input I would have is - eat the elephant one bite a t a time. The 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
April 30, 2019 at 5:46 am
Wait. Managed instance is different. They want that to be a lift & shift location. You can run a restore there. That's different than 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 29, 2019 at 4:36 pm
Reading execution plans is fairly complicated. Follow the link below, or look it up online to find a free book I wrote on the topic. Work tables aren't bad (or...
"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 29, 2019 at 2:13 pm
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
Viewing 15 posts - 2,596 through 2,610 (of 22,219 total)