Rajesh kasturi (7/31/2009)

---

Jeff,

I knew some ways to get rid of tempdb issue.

Why I posted the question is,

Who expects reply to this quesion.

I agree with you, I am still...

Yeah, I'm with Jeff on this. You can rely on TRUNCATE resetting to the original definition. I have not seen "0" popping up, ever, after rebuilding a table, truncating, or...

Actually though, that's what views are for. If you really don't want the internal's available, a view masks it perfectly. You could run into issues though if you see lots...

And then a thorough code review (we're talking proctology exam) to determine if there's one procedure with a problem or if there's a systemic issue with all the code being...

Documentation and discipline are about the only things that come to mind. I've never tried doing something like this nor heard of anyone doing it successfully.

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....

Ronnie.Patton (7/30/2009)

---

Thanks for the reply

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...

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.

Bad news. The only way I know to change physical column order is to drop & recreate the table.

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......

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.

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,...

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...

Sounds like a classic case of parameter sniffing. Do a search on that term. There are multiple ways to fix the issue.

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...