How can we help you today? How can we help you today?
mordy
Hi Brian, my initial plan was to host a webservice that had access to the database I would use as the template and from a local application on a client machine to have an application to synchronise the structure of a database with this master-template in order that we could easily reflect changes to MSDE databases running on client machines - our master database will be behind a firewall so I only really have port 80 to work with which is why the webservice is probably going to be my best option for peeking through it to register the master database to use as my template for the comparison. Plan A was a simple function in the webservice to register the database and return the created database object to the local client application which would then use it as the template to check against its' own local copy and synchronise any changes thereby radically simplifying deployment of new versions to the client by ensuring their local MSDE databases were always in synch with our release versions - it's become very easy to deploy new software revisions with .NET but there's always that nagging fear that we've added a column to a table and broken integrity with the local databases come release day and my evaluation project is to establish whether we can incorporate SQLCompare into a tool to take away this worry [image] The reflection seems to be something the framework is doing - that's a little above where I'm at on the .NET learning curve at the moment, in a nutshell what I need the webservice to return to the client application is a registered database object containing the structure of the 'template' database on our DB server. / comments
Hi Brian, my initial plan was to host a webservice that had access to the database I would use as the template and from a local application on a client machine to have an application to synchronise...
0 votes