Viewing 15 posts - 8,671 through 8,685 (of 22,219 total)
Yeah, I'm with Gail on this. I spotted the one issue, but I'm pretty sure you have others. But working off this vague set of descriptions the best I can...
"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 14, 2014 at 3:22 am
Hmmm... Not crazy about that approach in the script. Allen White has a script he uses to do the same thing. You might search his blog. I'll bet it's more...
"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 13, 2014 at 5:00 pm
All the memory is not too much. SQL Server has limits to the amount of memory it can use. You can see that here in the documentation. You'll want to...
"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 13, 2014 at 4:56 pm
You don't have b.Rank as one of the columns defined in the SELECT list that you're selecting from.
This is not a good practice, for some of the reasons you're hitting...
"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 13, 2014 at 11:43 am
george.auckland 44813 (3/13/2014)
USE [CTM_Reporting]
GO
/****** Object: UserDefinedFunction [dbo].[ufn_Banner_Orion_Employee_Comparison_parser_v2] Script Date: 3/13/2014 11:57:36 AM...
"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 13, 2014 at 11:20 am
You have to build the string. Just referencing the parameters won't work.
"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 13, 2014 at 11:15 am
I'd suggest trying some indexes on the table and using a JOIN to do the UPDATE.
"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 13, 2014 at 10:52 am
You have parameters that you're passing values to and then those parameters are used in your SELECT statement to return the values passed. That's how parameters work. What you're...
"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 13, 2014 at 10:50 am
It's a security error that's basically preventing you from making a series of calls to the OS. To run it, you have to do what it's asking for.
"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 13, 2014 at 10:44 am
Perry Whittle (3/13/2014)
is this a virtual machine, which hypervisor platform are using?
This is a VM running on Azure, which means, technically, the HyperV hypervisor although things are a little different...
"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 13, 2014 at 10:41 am
yuvipoy (3/13/2014)
Yes Col4 is having condition as (Col4>0 OR COL4 =200000000)
Fine, but where is it coming from? It's not a part of the query as outlined, so is that thing...
"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 13, 2014 at 8:30 am
Text plans... blech!
Anyway, like I said, you're getting a scan because of the function:
[SCM].[MEAS_VALUE]<>-1 AND [SCM].[COL3]&239=0
The other two scans are not as obvious. For example, this one:
[M].[COL4]>=0 OR [M].[COL4]=-2.01019e+009
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 13, 2014 at 7:52 am
I'd love to see the execution plans, but this little critter is going to prevent index use:
and ((c.col6 & 0XOEF) =0)
That's going to lead to scans, all the time every...
"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 13, 2014 at 7:17 am
If you have an account that has access to all the file shares that your backups are going to, you could use that account to run a powershell or batch...
"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 13, 2014 at 7:12 am
Never heard of it. But my response to one these is always the same, "Cool. Awesome. Can you show me a recovery to a point in time?"
If they can 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 13, 2014 at 7:03 am
Viewing 15 posts - 8,671 through 8,685 (of 22,219 total)