OK. That is odd then. I use this function regularly and it doesn't bump tempdb up to 20gb (I'd notice). Any triggers or anything like that on the table that...

It doesn't surprise me to see it in the tables with 50 rows. I ran into the same issue with tables that had less than ~200 rows.

The others... I'm not...

You can do this through Management Studio very quickly. Right clicking the object brings up a menu with "Script Stored Procedure as" and then another menu that has choices like...

We use that all the time with no serious issues. But then I've never monitored tempdb while running it. Are you breaking up your trace files or creating one gigantic...

How many rows are in the tables? I've seen this when the number of rows is very low. Other than that, rebuilding the index usually changes the fragmentation percentage.

So, would it be plagiarism to copy that from you?

At this point in time, keep your plans to work with 2000, but go ahead & skip 2005 and start learning 2008.

Take a look at the catalog views. Sys.Tables & Sys.Data_Spaces. This is quick & dirty:

select t.name as TableName

,s.name as FileGroupName

from sys.tables t

join sys.data_spaces s

on s.data_space_id = t.lob_data_space_id

I found a blog entry over at MSDN that talks about this:

http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx

If you scroll down to Message #10:

Reason:

1) There are spaces after Instance name in the...

I think you have something else going on. The delays are not normal.

Well it's about time.

Congratulations Steve! You earned it.

Hey Jeff,

Do you have that response in a script so you can just point & click? If so, can you share the script?

Hi Sandy,

When you run backups, don't use drive paths like this:

BACKUP DATABASE x TO DISK = 'C:\x.bak'

Because it will place them on the relative drive for that server. Instead,...

Not knowing your friend, the company, or the interview, it'd be impossible to say why. Usually, it's because the people doing the interview thought that someone else was more qualified...

Well, if you're lazy you can even get around that:

INSERT INTO dbo.MyTable DEFAULT VALUES

GO 42

I suspect that's not what was meant. I'd be curious if there was a method too.