You cannot. The auditing is done inside the SQL server so that the repository must be inside. If you want you can use available replication methods or create a DTS package to copy audit records from different servers into one central location. Just be aware that bringing lots of data across the network all the time has its own problems and can slow down everything. : I am currently deploying a test of v2.6 to various MS SQL Server. In my : inital test, I installed this on one machine but used an existing db for : the repository. Next I deployed it to a second machine an with its own : repository db. : Now, I want to deploy to a third machine. The problem is I want to use the db : that I created and not have to create a repository db on each server. Is : this possible?
|