SQL Monitor database (Data Repository) off-site

J_S

Is there any way the SQL Monitor monitoring service can be setup to push updates to a Data Repository without a direct TDS connection?

Are there examples showing the optimal way to push a Data Repository off-site for review? The only reference I saw in the documentation was in regards to moving the database. I tried to search the forums a bit, sorry if this has already been explained.

I would like to:

1. collect in production (using SQL Express / whatever)
2. disconnect (continuing collection in the next file)
3. move the collected data off-site
4. merge collected data into the "official" Data Repository

This would be useful to me anywhere from every 5 minutes to once a day.

Edit: It looks like official support for this is on the roadmap, but if anyone has already implemented this manually I'd appreciate it. Also, any general advice on merging two Data Repositories would be appreciated.

Russell D

The multiple basemonitor feature, which is already usable (in BETA), is the intended method for solving complex geographical setups, and I think it's what you are referring too when you mention the roadmap. I'm not sure that it's really aimed at the scenario you've described though.

Why do you want to disconnect the collected data file, to be moved off-site, for merging later on?

Just to clarify, this scenario (I think) you're describing is not on the roadmap.

J_S

I can manually migrate large files out of our production environment, but can't really make any connection between SQL Monitor and the Data Repository - especially not a permanent one.

Russell D

Ok, we certainly don't have any plans to allow merging in of other repositories at present, but it's definitely something we'd like to do as there are distinct advantages too it. Best place to put this is the SQL Monitor uservoice, fleshing out as much detail as you can.