Viewing 15 posts - 16,321 through 16,335 (of 22,226 total)
GilaMonster (10/14/2009)
http://www.sqlservercentral.com/Forums/Topic803081-338-1.aspx
Some else can have the pleasure of this one. I'm going to spend an hour trying to conquer the galaxy, then going 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
October 14, 2009 at 2:24 pm
forum member (10/14/2009)
I need help with sql query
I have bookings in one table and bookingstates in another table which contains states related to booking
Booking Table Schema ...
"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
October 14, 2009 at 2:22 pm
Yeah, what Gail said.
Seriously though, she's right. There was missing index information in the execution plan, it was moving scads of data around to retrieve 600 rows, you're getting 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
October 14, 2009 at 2:19 pm
Slick84 (10/14/2009)
Thank you for the information. Can you possibly point me to the right direction for updating stats on the tables as well as more information for "Full Scans". I...
"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
October 14, 2009 at 1:23 pm
You're getting a scan on the tblProductSizeWidthColor table, from the name alone, I think you've violated some design principals, which is reading, if I counted the digits correctly 332 million...
"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
October 14, 2009 at 1:03 pm
Sorry. It sounds like to do what you want, you need to make a change to the code.
"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
October 14, 2009 at 11:17 am
Yeah. This is untested psuedo-code, but it illustrates what you do:
CREATE PROCEDURE A
(@p1 int)
AS
EXEC B @p2 = @p1 OUTPUT;
SELECT @p1;
GO
CREATE PROCEDURE B
(@p2 int OUTPUT)
SET @p2 = 42;
GO
You can look up...
"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
October 14, 2009 at 10:35 am
s ss (10/14/2009)
Bob Hovious 24601 (10/14/2009)
This is why people who waste our time are irritating, as are the people who insist that their problems are urgent and somehow more deserving...
"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
October 14, 2009 at 10:23 am
In 2008 you could make a table variable and pass that between stored procedures, but you'd probably still need to make it an output parameter to get it back out...
"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
October 14, 2009 at 10:05 am
Can you post the execution plans?
"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
October 14, 2009 at 9:52 am
Excellent. Now tell me what color your parachute is and you're hired.
"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
October 14, 2009 at 9:48 am
An output parameter from Sp2 would be available within sp1. Have you tried that?
"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
October 14, 2009 at 9:40 am
It's possible to do a cascade delete, but to do a cascade update, not so much. You're not actually removing the address value, you're changing which one the customer points...
"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
October 14, 2009 at 8:20 am
Can you do it? Yes. Should you do it?
You're running into the same situation that lots and lots of people have run into with clustering. They're trying to have 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
October 14, 2009 at 7:56 am
However large the log file is, it is. There's nothing wrong with a large file. But... it does raise the concern that you're logging operations that should not be, that...
"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
October 14, 2009 at 7:50 am
Viewing 15 posts - 16,321 through 16,335 (of 22,226 total)