First, you could change your query to simply:

SELECT DISTINCT(id) AS id INTO #TEST1TEMP FROM TEMP1

But that is no answer to your questions. So here goes.

1) A temporary table is created...

So what do you want then? AFAIK, there is no way to see which log file is currently being written to. Why is it important for you to know that?...

Yes, each database will always have it's own table sysobjects with entries for all the objects in that database. However I am not sure about your understanding and use of...

I do not agree completely here:

1. Don't let data get into your database this way. The application should commit data to database they it wants it to be retrieved.

The database...

Could you provide more detail, preferably the exact steps that you take. Are you restoring to the same server? Are you using the standard built-in SQL backups?

Get a system that supports the newer dual-core processors and consider purchasing either the dual-core processors because MS license baed on physical processor not logical. So in effect 1 processors...

Are you also using SQL Server 7 as the original poster in this old post did? And can you post the exact steps you followed to shrink the file? Are...

Since the temp table is not created in your user database (and also is not created with the name you use for it, in reality it has a suffix also)...

SELECT REPLACE(@string, '

', '')

You can remove BUILTIN\ADMINISTRATORS from logins.

Since there are only two possible values to index I do not think the indexes would do you much good. Unless there is a very small amount of the values...

Create a user in the database with no permissions other than the right to access the database. Then add that user to the db_datareader fixed database role.

Hmm, I can't think of a way to do this. Why do you need this?

Here's a sick idea

Not quite sure what you meant with this, other than that it came slightly closer. I also tried this in SQL Server 2005, and got results 62%...

59% to 41% on the execution plan

And if you add an index on (Customer_Id, Last_Billed_Date) you are at least in a little better shape: 53.55% against 46.45%