Now .... unleash the beast :w00t::smooooth:

btw: No problems overhere after switching db_level...

- IMO this post is placed in the wrong forum (discuss content posted by BockWoody ??)

- Start with MS SQL2005 upgrade advisor (analysis your sql2000 db)

- fix the problems it...

Indeed, domain service accounts are in use.

The SSIS service account has been granted privileges on MSDB.

My windows account has sysadmin auth at the db-server (sqlserver).

- Maybe creating a DTS package to load your tables may be the way to go, because it has the option "keep identities"

-If using set identity_insert on, keep in mind...

If I recall correct there has been a web based MS application for sqlserver that was able to script out the ddl and then insert statements for sqlserver 2000. (SQL_Server_2000_Web_Services_Toolkit...

-As long as you dont forget to migrate and sync the users, it should be OK.

-Also keep in mind te perform full db maintenance after the migration.

(rebuild indexes,...

Indeed, for the moment we're doing some test to...

Maybe even a view can help out, pointing to a staging table where your active inserts happen during migration time.

Selecting from both the "old" table and the staging table.

Copying data...

check out convert(datatype, yourcol, format)

Thanks for the ref. I'll check it out in the weekend.

It was some part of the dotnet framework 2.0 that got messed up.

I unstalled it and tried to reinstall (from...

- your sqlserver instance will be able to run on both nodes.

- You'll have to perform an extra install if you also want to have SqlServer Management Studio available at...

if someone has dropped the index/table during your operation, it is obvious your statement fails.

set nocount on

declare @OnlineRebuild char(1)

Set @OnlineRebuild = 'Y'

print '-- Begin ' + db_name() + ' ...

One way of handling that in vb or .net is to use variables declared as DateAndTime.

Don't stuff it into strings, ... but use the corect variable-datatype.

IMO the behaviour you describe is applicable when you run a :

create table mytable (col1) ;

in that case no...

So he gets an error when executing :

create table dbo.mytesttable (col1 int not null)

:unsure:

Very strange.

How many schema are defined in the db ?