Post reply

Checking database integrity between two 'supposedly' identical databases

  • July 4, 2011 at 8:47 am

    #238969

    Hi,

    I want to know the best way of comparing two databases that are supposed to be identical?

    Thanks

  • July 4, 2011 at 8:51 am

    #1347904

    Red-Gate has a trial for sql compare and sql data compare.

    I have some script but they are to rudimentary to share.

  • July 4, 2011 at 8:56 am

    #1347909

    Red Gate's SQLDataCompare comes to mind immediately

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • July 4, 2011 at 8:58 am

    #1347912

    I have used all my grace trials... and it is on a production server.

    I dont really want to install anymore 3rd party apps on it that will take up space.

    Thanks

  • July 4, 2011 at 8:59 am

    #1347914

    nathanr 81822 (7/4/2011)

    I have used all my grace trials... and it is on a production server.

    I dont really want to install anymore 3rd party apps on it that will take up space.

    Thanks

    Sure, then waste 80 hours writing your own app.

    As a side note. You could move the dbs on another server, then re-install the trial there and fix your stuff.

    As a final note, if you keep needing to use the same app over and over again, then maybe it's time to BUY it.

    Kool 16 000 :w00t:.

  • July 4, 2011 at 9:04 am

    #1347919

    You don't actually need to install it on the server. You can install on a workstation, though then the compare will be slower because of moving all the data around.

    Seriously, it's going to be cheaper to buy the product than to try and write your own. Comprehensive data compare is not trivial.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • July 4, 2011 at 9:36 am

    #1347936

    I totally agree with installing it again and comparing the db's from another machine.

    Thanks

  • July 4, 2011 at 9:39 am

    #1347939

    [General comment]

    It always amazes me when I see a software dev go out of there way to save a few $ on a license and then complain when someone does the same to them. :hehe:

  • July 4, 2011 at 9:45 am

    #1347942

    I totally agree. 🙂

  • July 4, 2011 at 10:24 am

    #1347968

    GilaMonster (7/4/2011)

    You don't actually need to install it on the server. You can install on a workstation, though then the compare will be slower because of moving all the data around.

    Seriously, it's going to be cheaper to buy the product than to try and write your own. Comprehensive data compare is not trivial.

    I wouldn't recommend installing any of the SQL comparison utilities on any server. They are all written as a client tool and should be installed on a workstation. Installing on a server would only reduce any performance hits if you always compared database on the same server. Generally, you are going to be comparing DEV to QA (different servers), QA to UAT, and UAT to Live.

    I have to tools - and I find that I use the schema comparison the most often because I compare the systems between environments and don't need to compare the data. When I do need to compare data - it generally is specific tables in each environment (e.g. lookup/dictionary type tables).

    For the cost of the tools - they have already paid for themselves several times over.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • July 4, 2011 at 10:31 am

    #1347970

    Ya 395$ to 595$ is a joke compared to 4-5 weeks developpment time to do any remotely similar-ish.

    Even the full toolbelt would be free compared to that... specially since you seem to have multiple uses within 1 year.

  • July 4, 2011 at 10:37 am

    #1347973

    Jeffrey Williams-493691 (7/4/2011)

    I wouldn't recommend installing any of the SQL comparison utilities on any server. They are all written as a client tool and should be installed on a workstation. Installing on a server would only reduce any performance hits if you always compared database on the same server.

    If you're going to be doing automated comparisons (and/or syncs) with the command-line tools, then I would put it on a server (probably not prod though). Otherwise yes, it belongs on a workstation.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • July 4, 2011 at 10:49 am

    #1347975

    GilaMonster (7/4/2011)

    If you're going to be doing automated comparisons (and/or syncs) with the command-line tools, then I would put it on a server (probably not prod though). Otherwise yes, it belongs on a workstation.

    Since I have never use the automated process - I keep forgetting about it. Really have never found a situation where automating this is worth the effort, but then again - I support mostly vendor supplied applications.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

Viewing 13 posts - 1 through 12 (of 12 total)

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