Re: ISO: sql server table comparison utility

On Sep 21, 1:16 pm, "tom.rmadilo" <tom.rmad...@xxxxxxxxx> wrote:


Is it just differences in data, or has the data model also changed?

Only data has changed. However, the vendor product uses hundreds of
tables. We are trying to trim the number down by ignoring ones that
are used by modules we do not yet use, or that contain data that we
know we don't care to compare. That still leaves quite a few tables
that need to be compared.

We've picked three to start with, just to see the level of effort.




I can tell you that it will be much faster if you can use database
operations for the comparison. It will be several orders of magnitude
faster and will likely be much more accurate. (If you can't use the
built in sql or pl language, probably you can use another language
supported by sql server.)

Because of the volume of tables, and our lack of expertise with the
tables, writing hundreds of sql comparison scripts is more effort that
I expect we are prepared to commit to.


Another possibility is if you could create a dump of each database and
then run a standard diff, this might at least quickly identify how big
a problem you have on your hands.


This is sort of what I am trying - to go to the database, export
specific tables to csv. First problem I hit was that the sql table had
a column with a weird type that doesn't show up when we look at the
table from within the application - whee! When I got around that, I
found that my microsoft tool was out of sync with the actual sql
server database - so now I'm awaiting that upgrade.

Eventually, I'll get a couple CSV files - then I can at least diff
those (and, if needed, use Andreas K's csv module from tcllib to
twittle a bit) to get a rough idea of the differences.

I just had hoped that someone had run into the same idea - develop on
one database instance, then, before migrating that data to production,
generate a report of the differences for the tables that are going to
be migrated...
.

Relevant Pages

  • Re: Exporting SQL Server database
    ... The tools distributed with SQL Server are woefully inadequate for this task. ... Every RDBMS will have data dictionary tables/views that you can query to discover what tables are in the database, their structure, etc. ... If you output csv instead of SQL take advantage of the csv module in tcllib instead of reinventing the wheel. ... If I had access to a MS SQL Server database I'd be willing to write a script to do the job for you ...
    (comp.lang.tcl)
  • Re: CSV file as database
    ... Seems that I've caused this CSV input thing to drift two a couple different threads. ... I now have a process that gets my CVS into MySQL without too much fuss. ... That allowed me to create a database with nothing in it. ... Once the database was created, there was a command button called SQL, that offered a panel into which SQL commands could be typed. ...
    (microsoft.public.dotnet.languages.vb)
  • File import and performance
    ... 20,000 entries. ... the data from the csv file along with the product number into a database. ... but I'm not sure SQL can do what I need to do. ...
    (microsoft.public.sqlserver.programming)
  • Fixed
    ... I also found this article that gives the proper way to move system dbs in sql 2008: ... The model exists where the master states it exists. ... This is the error log prior to detaching the model database. ...
    (microsoft.public.sqlserver.server)
  • Re: CREATE AGGREGATE failed because type Concatenate does not conform to UDAGG specification due to
    ... Go to the Database tab and click on the browse button next to the connection string. ... In the New Database Reference dialog, enter the details for the database where you want to deploy the assembly and create the user defined aggregate. ... I'm trying to do some CLR integration with sql server 2005. ...
    (microsoft.public.sqlserver.programming)