"Working with tempdb in SQL Server 2005"

http://www.microsoft.com/technet/prodtechnol/sql/2005/workingwithtempdb.mspx

addresses several of your points.

Regarding your #2 question, yes, there are times when it makes sense to break up large inserts, updates, and deletes....

What about using synonyms? One downside is that you would have to drop and create them every month much like the view definitions.

create table TestIt (a int, b int)

create table...

For "homegrown" replication, I would do the transformations in stored procedures. That's more out of personal...

Many ways to do this. Here is a simple one to get started

select *

into #a

from information_schema.columns a

where table_name = 'aaa'

select *

into #b

from information_schema.columns b -- add linked server name and...

Mind you, this sort of thing is a band-aid, quick and dirty fix and should not be used on critical stuff. If you are going to be stuck with the...

Add triggers to the A tables. Depending on how the tables are set up and how many changes they get, and so forth, you could have the triggers write to...

You can switch compatibility level on the fly without turning anything off. However, before you switch you should look for things that may break. There are gotchas. See sp_dbcmptlevel in...

Because you can't change context like that. Can't do it in a procedure either. Basically, "USE xyz db" only works in a query editor.

-- Parts 1 and 2 are to be run in Query Analyzer

-- PART 1 Make a table to hold the results

if exists (select 1 from information_schema.tables where table_name = 'DBGrowthRate')

drop...

you have to

CREATE PROC [dbo].[up_UtilDBGrowthRateSql2000]

before you can

ALTER PROC [dbo].[up_UtilDBGrowthRateSql2000]

Which means, run all of the code ONCE with the create statement. After that, if you...

Fortunately, I just did this a few months ago. The PART 2 part that runs every day or so is in this procedure. Note the revisions to the table layout...

that's because you threw the /B switch. /B means Bare--only filenames.

You are missing a slash in @Path. You have c:\Personal*.txt not c:\Personal\*.txt.

declare @Path varchar(128) ,

@FileName varchar(128)

select @Path = 'C:\Personal\' , ---<<<right here

@FileName...

What you want to do is not directly possible. However, as Young says you can get the results with dynamic sql. You can also get them without dynamic sql by...

Willing to be wrong here, but I do not think there is a silver bullet for this. Any job could run a proc, OS command, etc that connects to another...