upgrade database

Question

upgrade database

SQLIndia

Ten Centuries

Points: 1073
More actions
April 25, 2005 at 9:03 am

#163372

Hi Folks
I have situation here about upgrading databases.. under same sql server group. From database to another database....
1. I need to know the structure of upgraded database.
2. If any data in tables of upgraded database and if any, then export them out in data text file to upload them later by Bulk insert method..
3. steps I should be kee in mind to do this kind of activity.
thanx in advace folks
sonny
singhsonny@hotmail.com
SqlIndia

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Mike Metcalf SSCrazy Eights Points: 8763 More actions · Answer 1

It would help us if you could give us some idea of what you're upgrading from and too, and also the size of the DB would be beneficial.

Can you pad out the information a bit to give us a chance?

mark baekdal-145375 SSCrazy Points: 2200 More actions · Answer 2

check out this article/white paper (it was also published on this site) http://www.innovartis.co.uk/pdf/Innovartis_An_Automated_Approach_To_Do_Change_Mgt.pdf . DB Ghost (http://www.dbghost.com) has been built using this document.

regards,

Mark Baekdal

http://www.dbghost.com

http://www.innovartis.co.uk

+44 (0)208 241 1762

Build, Comparison and Synchronization from Source Control = Database change management for SQL Server

SQLIndia Ten Centuries Points: 1073 More actions · Answer 3

Thanx for response guys ...

Mike Metcalf: here it is detail of upgrade situtaion..

database size is not very big.. just 300 mb.. There ofcourse two databases.

1.one upgrade from another one. data must be export out either using bcp or DTS.. from both databases..

2. Then empty the upgraded database and upgrade from other database(from which should be).

3. Then upload daa into upgraded database..

Problem..

1. tables structure e.g columns, rows etc..

2. data for same table sfrom both database..

3. key or index, defaults, UDF and UDT etc. handlings..

so, this is samll upgrade but little new for me...

I hope you will have answer for me..

thanx in advance

swarn singh

SqlIndia

Mike Metcalf SSCrazy Eights Points: 8763 More actions · Answer 4

Hi Swarn,

I'd agree with the former poster that something like DBGHOST or SQLCOMPARE (and DATACOMPARE) would be, we use SQLCOMPARE extensively in our organisation and have found it to be more than up to the job.

I don't know about DBGHOST but I know you can get a free 30 day download from Redgate (i'm sure DBGHOST will do a similar deal).

Hope this helps

mark baekdal-145375 SSCrazy Points: 2200 More actions · Answer 5

Yes DB Ghost does a 30 day evaluation although it is very different from Redgates SQL Compare and Data Compare. This is a summary of the differences: http://www.innovartis.co.uk/FAQ_DB_Ghost_vs_Diff_Tools.asp

to summarize the above web page:

Here are some of the main differentiators:

a) DB Ghost works with scripts and therefore with all Version (source) control systems. It works in harmony with configuration management best principles. SQL Compare has no concept of this whatsoever.

b) Quality of Upgrade delta script. DB Ghost will produce a script that is guaranteed to work and SQL Compare doesn't (look at their FAQs)

c) Price. For purely comparing two databases SQL Compare is cheaper than DB Ghost by a long way. However, if you want to run SQL Compare from the command line you must buy the Toolkit option which makes the Red Gate offering considerably more expensive than DB Ghost (it has always been possible to run DB Ghost from the command line)

d) User interface. SQL Compare allows you ultimate flexibility in choosing which objects to include in the delta script. DB Ghost does not offer so many choices as we believe that this kind of ad-hoc ‘promote this but not that, oh and, I nearly forgot – this as well’ approach is manual and, therefore, ‘human error’ prone.

e) Comparison speed. SQL Compare is quicker than DB Ghost at determining the differences between two databases. This advantage is generally nullified by the inherent problems with only comparing two databases and not using source control. For example: If your developers use a shared database for development and you want to promote the changes to the test system you can do a lightning quick compare and get a list of the differences. What then normally follows is an excruciatingly error prone process of working out what changes are actually required and what changes are just ‘developer trash’ – i.e. stuff created during the creative phase of development. Usually this part of the process involves lots of communication which can be open to misinterpretation and therefore lead to broken deployments. Using DB Ghost you simply label the entire set of scripts and perform a build, compare and upgrade in one simple step. This can be automated as well freeing up even more time as it could be scheduled to run overnight as part of a daily build process.

SQL Compare is a great tool for getting you out of a hole as it lets you fiddle with your databases or simply make them the same. This gives you no audit trail whatsoever and could never be described as a change management process, it is simply change propagation.

DB Ghost is more expensive but is a true change management solution that will allow you to fully utilize your source control system to provide a full audit trail. It also scales – you can have hundreds of developers making hundreds of changes a day to your SQL Scripts and yet see virtually no increase in the overhead required to get them deployed. With the SQL Compare option your overhead increases with the number of developers.