Shared Database Over Different Domains
I have BarTender 10.1 Enterprise Automation edition. We set up our MS SQL server and library on a server on Domain_A. We need computers on Domain_B to be able to connect to to the system database on Domain_A so that they have the same library. Is this possible? If so, how? I read in the forums that WAN connections are possible, but nothing said how. When I try and use the System Database setup wizard and use the TCP/IP address I get an error message stating "A connection to SQL Server "XX.XX.X.XXX/NAME" could not be made." and the server is not on the list when browsing for BT System Servers. Any advice would be much appreciated.
-
It this situation it's best to have a BTSDB running in each domain and sync via replication between the two.
Although there isn't a direct way to just export the BarTender documents and files (and their revision history) from Librarian, and then import these documents to a different Librarian instance, you will be able to make use of replication in SQL Server. We already have a customer actually doing this (SQL Server replication). Attached you'll find information on how to configure it:Additional notes from our developers:- Replicating only Librarian and Security Center tables works best. According to our developer, trying to replicate additional tables besides this can be problematic due to their possible size.- For bi-directional SQL Server replication, I find it to only work for very specific set of conditions. Transactional replication w/updatable subscription is the best bi-directional method to use and is only available in SQL Server 2008 R2. Other versions of SQL Server do not have this method.- We strongly suggest to thoroughly test this type of setup.- Replicate only Librarian and Security Center tables:LibActions LibClients LibFileNodes LibFileStates LibItemBlobs LibItemPreviews LibItemRevisions LibItems LibItemTransactions LibUsers SystemData*If you don't wish to replicate the Security Center settings you might want to avoid the "SystemData" table.- For replication of large data, the Max Text Replication Size will need to be increased. If you run into this issue, you will see the following message usually "Length of LOB data (78862) to be replicated exceeds configured maximum 65536"You can increase the Max Text Replication Size by doing the following (This is applicable for transactional replication only):a. Execute the following SQL command:EXEC sp_configure ‘max text repl size’, 2147483647b. In SQL Server Management Studio:- In Object Explorer, right-click a server and select Properties.- Click the Advanced section.- Under Miscellaneous, change the Max Text Replication Size option to the desired value.- Our development department contact also found this website to be helpful:The idea of using SQL Server replication is in order to:• Rreplicate the Librarian tables from the BarTender System Database between two SQL Server instances.• As soon as replication is set up, all "Librarian" tables are now available on both instances of SQL Server.• Once the second server and BarTender System Database has the Librarian tables, Librarian will also show a copy / replication of these BarTender documents and their revision history on the second, separate computer.• Once this happens, you can stop to replicate both databases and now keep using only the second Librarian instance.I hope the above is helpful.0 -
participate listened :) 0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
2 Kommentare