that's one of the things they did not alter for sql2005.

You still have to mention the filegroup for each index and there is no setable default (other then the normal...

A default instance for sql2000 uses the reserved name MSSQLSERVER;

If you stated MSSQLSERVER for your named instance, you may be in troubles !

Be specific and mention the names you've used.

maybe this will help out ....

I don't have the ref where I got it

CREATE TABLE #tables_usage (

    name varchar(50) NULL,

    rows varchar(15)...

here's a very good article ...

http://www.sqlskills.com/resources/Whitepapers/Partitioning%20in%20SQL%20Server%202005%20Beta%20II.htm

use yourdb

exec sp_helpfile

you may want to add following startup-parameters to your sqlserver so you get a glimp regarding deadlocks...

-T1204

-T3605

to activate this without stop/start :

--dynamisch activeren

 dbcc traceon(1204, 3605, -1)

but add the...

- also upgrade to sp4.

- what kind of connections did you allow for sqlserver

  (sqlserver serverproperties network-config)

...Not that I expect that anyone would run out of drive letters...

- consider a cluster-node with a couple of instances topology driv1-data1 drive2-data2 drive3-log drive4-backup .... You'll run out of...

If you want the identities to start using your specific startvalue, you should specify it when adding the identity-column. Not afterward with a checkident !

Check books online !

regarding the reseed,...

or direcly

ALTER TABLE UsersImport ADD userIdInt int IDENTITY (99,1)

or build the alter dymamic :

declare @stmt varchar(4000)

select @stmt="ALTER TABLE UsersImport ADD userIdInt int IDENTITY (" + convert(varchar(15),@yourvar) + ',1)"

exec (@stmt)

No problem

SQLServer publishes itself !

If you don't change the servername, there is no problem.

IPaddress changeing is no problem, as long as your applications do not connect directly using the IPaddress...

...but existing objects could not make use of the secondary filegroup?...

- If you don't alter existing objects (tables or indexes), they will not use the new filegroup ! You have...

- and off course there should be space at disk-level

- your db already has a filegroup named 'secondary'

   choose another name. contact your...

- use xp_fixeddrives to check out your current freespace at the "local" drives.

    (this proc may be secured)

- there may be file-latency when extending a datafile (from your primary filegroup)...

how about (b)locking issues, long running requests,...

sp_who2, sp_lock may help out