After the other REPLACEs, you might as well replace all multiple spaces with a single space, to avoid any possible issues with, for example, "  AS  ".   The actual REPLACEs...

Even if the db is not normally in SIMPLE mode, you would certainly want it to be in SIMPLE for these rebuilds, to drastically reduce logging requirements.

If the...

• This reply was modified 5 years ago by ScottPletcher.

With a table that large, say you have a total of 6 indexes, 1 clus and 5 nonclus.

I'd expect it to be faster to do a REBUILD...

ONLINE rebuilds must be fully logged.  Make sure you have pre-allocated enough log space to handle the ONLINE rebuild before issuing the command.

Then, try an ONLINE rebuild on an index. ...

Even if the db is not normally in SIMPLE mode, you would certainly want it to be in SIMPLE for these rebuilds, to drastically reduce logging requirements.

If the db is...

Btw, I suggest not using the term "magical tables" in your interview.  It sounds rather unknowledgeable about relational dbms's.

Oh, virtual tables.  Yeah, SQL has lots of virtual tables.

Yes, you could easily be asked about the inserted and deleted tables.  You can treat these as regular (physical) tables in...

I intended that you would get a specific row's(s') actual physical length(s) based on the input to the function.

You specify a unique key or key range for any existing unique...

With a table that large, say you have a total of 6 indexes, 1 clus and 5 nonclus.

I'd expect it to be faster to do a REBUILD ALL than to...

If a job has only 1 step, then that step started when the job itself started, and you already know how to tell that.

It's long past time that SQL Server should provide a ROWLENGTH function that gives you the physical length of a row(s).  But that's likely just wishful thinking on my part.

Use REBUILD ALL, it will (should) be more efficient.

But pre-grow the log first to the total size you will need for the REBUILD.  It's a very slow process when the...

Of course the lazy way to get an accurate avg row size, if you have the time to let it run, is using:

EXEC sys.dm_db_index_physical_stats

specifying 'DETAILED'.  SQL will then calc the...

I don't know your data.  In the original q, you stated "each day of the week".  So I guessed one week.

If you only need two days, then change the ending...

I've been a SQL Server DBA for 20 years, I've never heard of "magic tables" in SQL Server.  You need to be clearer and more specific about what you're trying...