Just as a warning, a job can only be running once at a given time otherwise the sp_startjob will fail.

What I mean by this is that if you have a...

I can't answer your question, exactly... but SQL 2005 does have more intelligent lock manager.

I've scoured the msdn blogs for the article I read about this, but couldn't find it......

If you're inserting data in a sequential manner according to your index, you will probably not need to reindex. If the data is random compared with your index, you...

yes to all.

I thought your other questions were example questions.

It's the same thing as a regular reindex, only when you specify a partition, only that partition is reindexed.

Oh, and specifying...

If you've not disabled builtin\administrators I'd look there.

Lots of times development groups put themselves as local admins on their server because it's less headaches. It's not an obvious place...

Yes,...

Can you get it from systypes?

select * from master.sys.systypes

I'm not quite sure if that's what you're meaning in your question.

I think what you're essentially talking about is an ETL job.

You might consider a couple of options.

1. Use your OLE DB provider as a datasource in SSIS; use agent to...

If it's disk space you're meaning, there are a number of ways.

I usually run

xp_fixeddrives

to check the available drive space. FYI It doesn't work if you use...

Another good solution that was not mentioned before is to use database mirroring and a snapshot of the mirror. Depending on how current the data needs to be, this...

And besides all that, the answer of what happens when you compare strings with >= entirely depends on your collation setting.

under normal circumstances >= in varchar/nvarchar means...

If you're just talking about the database considerations, there are none.

Standalone to Cluster is not an issue for databases, the only differences are at the instance/server level and those things...

I believe you can use the copy database wizard to move jobs.

Just set up a 'sacrificial' database, right click -- tasks -- copy database

Run through the Wizard and I think...

On more hint if you go that route: Put the db in restricted_user mode first... Even though it's an online operation, nobody wants to see all the incorrect references in...

an idea that might work would be to add an 'oldkey' column to your prod database, pump the data from old to new and allow the new db to assign...