Viewing 15 posts - 16,831 through 16,845 (of 22,221 total)
I agree. Other than masking the columns behind a view, there's no real way to do this.
BTW, that's by design. SQL Server is not meant to be the presentation layer....
"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 30, 2009 at 11:58 am
Ronnie.Patton (7/30/2009)
We will most likely be doing its a reports database that needs to be a copy of the production database at some intervial behind. 1 hour...
"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 30, 2009 at 11:16 am
Thanks Jeff. I wasn't sure whether or not to suggest the nested set approach. I don't have any experience with it, but I knew it was a possibility.
"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 30, 2009 at 10:28 am
Bad news. The only way I know to change physical column order is to drop & recreate the table.
"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 30, 2009 at 9:22 am
OK. So how are the bogus fields identified? In client code or TSQL? If on the client side... 20 calls might not be that expensive. If on the TSQL side......
"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 30, 2009 at 9:20 am
Thinking about it a bit more... do the 20 rows come from the results of the procedure? You might want to look at the OUTPUT clause... I'm guessing here.
"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 30, 2009 at 8:30 am
Order of the columns in the key may or may not break down the way you're talking about. It depends on what the optimizer does. As a starting point, yeah,...
"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 30, 2009 at 8:21 am
It's only four columns? I'd suggest you look up a method written by Jeff Moden that uses a tally table to break down a comma delimited list. That's probably going...
"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 30, 2009 at 8:19 am
Sounds like a classic case of parameter sniffing. Do a search on that term. There are multiple ways to fix the issue.
"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 30, 2009 at 8:17 am
SELECT INTO with a linked server and that much data is going to cause you a lot of headaches. Linked servers move the data being processed from the linked server...
"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 30, 2009 at 7:38 am
I have yet to put this into production, but in the dev & test servers where I've been using compression there are many positives regarding reads. The writes don't seem...
"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 30, 2009 at 7:35 am
bhavesh_183 (7/30/2009)
I have fairly huge table having 1 million records. The table has a binary tree structure.
I want to write a procedure for getting all the children records 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
July 30, 2009 at 7:14 am
Since the query is currently running, you may need to use sys.dm_exec_requests. This will provide you with a current statement start & end offset so that you can see which...
"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 30, 2009 at 7:00 am
It depends on what you want to do. You can use sqlcmd to run command line scripts to move data from 2008 to 2000 & vice versa. SSIS will 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
July 30, 2009 at 6:56 am
To answer the question, it's going to be approximately a wash. Replace acts as a drop & recreate.
But, I'd suggest pursuing what happened as well. What do the consistency checks...
"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 30, 2009 at 6:50 am
Viewing 15 posts - 16,831 through 16,845 (of 22,221 total)