You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Audit Trail - USe Multiple SQL servers? - feature request

Audit Trail Ideas
Updated June 25, 2020
posted on January 31, 2015 • Show version history

In our environment we have SQL servers for production loads and other SQL servers for test/dev loads.

Our Laserfiche server has repositories in both test and production classifications.

It seems that audit trail allows only connections to one SQL server for all repositories.

I'd request that the configuration be updated so that each repository can have its own sql server specified.

Otherwise, I have to have Audit data for prod repositories on a dev SQL server, or dev repositories on a prod SQL server.

Or... is there somewhere I'm missing?

1 0
replied on June 25, 2020

It would be nice if you could configure multiple SQL servers for Audit Trail to communicate with even though you can install a different copy of Audit Trail on another server.

0 0
replied on February 2, 2015

You can install multiple copies of Audit Trail on different machines.

2 0
replied on February 2, 2015

Well, that's true...  : )

 

For now we have this on one server.

0 0
replied on November 3, 2017

I expected you could specify different SQL servers (or instances) for different environments too. We have a client running production and UAT systems on the same server but using different SQL instances. It seems we can't do the same for Audit Trail though which seems odd.


Are there any plans to change this? I can't think of any logical reason why it shouldn't be possible currently?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...