Viewing 15 posts - 16,981 through 16,995 (of 22,226 total)
Sounds like you just want a JOIN. Read the article Gail suggested and post the code you've tried so far.
"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
July 17, 2009 at 7:48 am
I agree with Gail, hardware is not the place to start, especially since it appears that you've got a pretty strong system. Have you systematically collected performance data on 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
July 17, 2009 at 7:42 am
Try Ross Mistry's book, SQL Server 2008 Management and Administration. It's pretty good. For just a "what's new" point of view, Rob Walters' Accelerated SQL SErver 2008.
Neither of these will...
"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
July 17, 2009 at 7:36 am
Some of those views are deprecated in 2008. Get used to using DMV's for this type of data. Here's a script from Technet
select
t1.resource_type,
...
"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
July 17, 2009 at 7:32 am
Oh, and run a consistency check before the migration and after the migration. Paranoia...
"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
July 17, 2009 at 7:21 am
Just be utterly paranoid. Take a backup before the move. Take a new backup after the move from the new server. Keep both on the side for a few days,...
"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
July 17, 2009 at 7:07 am
Well, the reason I'm suggesting you need to define the clustered index as a seperate step is because, it doesn't necessarily come from the primary key. Don't confuse the two...
"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
July 17, 2009 at 6:01 am
Yeah, you're making sense, apparently I'm not.
I didn't mean that the child table would have those values, instead it has the FK to the PK of the parent, right?...
"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
July 17, 2009 at 5:57 am
You might try changing the order of the table definitions. I know everyone says that doesn't make a difference, but what they mean is, it doesn't normally make a difference....
"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
July 17, 2009 at 5:42 am
yeah, it shouldn't be an issue.
Let's assume your data looks something like this:
Columns in Table 1:
ParentID KeyVal1 KeyVal2 Some Data
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
July 16, 2009 at 8:57 pm
TheSQLGuru (7/16/2009)
"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
July 16, 2009 at 12:33 pm
zach_john (7/16/2009)
SELECT Top 1 @ContainerUUID=ContainerUUID
from CM_VENDOR_CONTAINER(NOLOCK)
where IsNULL(VENDorContainername,'')=IsNULL(@VENDorContainerName,'')
And IsNULL(VENDorContainerID,'')=IsNULL(@VENDorContainerID,'')
And FileUUID=@FileUUID
CREATE TABLE [dbo].[CM_VENDOR_CONTAINER](
[ContainerUUID] [uniqueidentifier]...
"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
July 16, 2009 at 11:44 am
GilaMonster (7/16/2009)
Nope. Noncluster. This was SQL 2000.
Hint:
SELECT count(*) FROM sysindexes WHERE id = OBJECT_ID('TableInQuestion') AND name LIKE '_WA_SYS%'
Ah.... Cool. I hadn't thought of 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
July 16, 2009 at 11:30 am
GilaMonster (7/16/2009)
"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
July 16, 2009 at 10:42 am
Jeff Moden (7/16/2009)
Think "parameter sniffing" to determine how far you'd carry the approach and when you can least afford for it to occur.
Yes, true. But there's good & bad 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
July 16, 2009 at 10:32 am
Viewing 15 posts - 16,981 through 16,995 (of 22,226 total)