The "how to" of this depends on what type of database system you are
using. We have setup multi-database implementations using SQL Server
and one DSN (you use a view from your authentication database to the
accounting database for the calls table and make the triggers on the
calls table, in the accounting database, update tables in the auth
database). You can do this using remote stored procedures with SQL
if its not the same SQL Server as well.
To try and clarify what I said earlier, the issue with using two
different DSNs is when you try to use some of the advanced features
of RadiusNT, like concurrency control, with the manual update options.
The manual update options run on the accounting thread (since they
happen when you received accounting requests) and therefore are
on the accounting database connection. This can cause those advanced
features to not correctly, or at all.
-- Dale E. Reed Jr. (email@example.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com
For more information about this list, including removal, pleasesee this URL: http://www.iea-software.com/maillist.html