Terry,

How do you reconcile the full schema "official version" from what is represented by the developer's change scripts?  This is a necessary step in any approach that tries to use two...

I think that about covers it for processes that are likely to deliver any real benefits.

Of course there are always many other "processes" that people employ such as in one...

Take a look at DB Ghost (http://www.dbghost.com or http://www.innovartis.co.uk) - it's been in the market for about four years now and it allows you to version all database objects...

It's amazing what people come up with as a "change management" process but I've never encountered that kind of madness before...did someone mention ITIL training?  I think it's just basic common...

Here is the obligatory message from me - even if you use the Upgrade Advisor and change the compatibility level to 90 your database could be broken and you won't...

Hi Colin,

Have you tried using DTS to transfer an entire schema? It's quite frustrating, basically DTS doesn't seem to bother with any...

Actually - restoring or re-attaching a SQL 2000 database and then setting it to 2005 compatibility will *always* work as SQL Server doesn't check anything - you're just changing a...

To have a completely clean and unbroken database you should script out your SQL 2000 database and cleanly rebuild it on SQL 2005. This has the advantage of explicitly...

Hi Keith,

if you use sp_executesql then you can use an nvarchar(4000) - would that be long enough for your needs?

Alternatively you could manage your changes using one of the many...

There are some things on MSDN regarding breaking changes here. However, there are clearly some changes that have not been published or have been overlooked (have a look...

One thing to be wary of when moving databases from SQL 2000 to 2005 is that, if you want to run in full 2005 compatibility mode (level 90) then you...

Are you asking for a proscribed way of limiting access? If so, there are many ways to achieve this but my favourite first step is, as Colin quite rightly...

If you are thinking of moving a database from SQL 2000 to 2005 then you need to be aware that your schema may be broken by the move without you...

Hi Dale,

Sorry - I missed your reply to my original post and I was just trawling through my old posts...

I think you misunderstood my point. I wasn't saying that...

You don't have to wait for .Net 3.0 as it is a superset of .Net 2.0 with WPF, WWF etc. tacked on.

i.e. as far as SQL 2005 is concerned you...