Hello, We've a large SQL2000 DB which is 335GBs in size and a majority of tables are geographically replicated to a subscriber using transactional replication across a 10Mbit line. We're going through the process of converting the DBs' environment to SQL 2005. Unforetunately I think this means...
Can SQL 2005 DB mirroring work if the mirror server is to be in another building (building networks connected via VPN router)? We just want employees to be able to remote into the mirror server from home if power is lost at the main building.
I have a server running sql 7.0 and I need to move the msdb database to another server running sql 2005. When I try to restore the db from a backup I'm getting a compatability error message. Any suggestions greatly appreciated.
I am trying to connect to a remote DB on a UNIX server. I am using embedded SQL statements to achieve this task. I have a file that contains DB name, ID & PW that I pass to the connect statement, rather than hardcoding the info to the program (for security reasons). C EstConnect BegSr ...
What issues do I face with database file compatibility if I migrate from 32-bit SQL Server 2000 to 64-bit SQL Server 2005?
Can I have multiple Distributors configured on one SQL Server instance? Also, can I have multiple Distributors configured on one SQL Server instance? Finally, can I have multiple Subscribers configured on one SQL Server instance?
SQL Server, SQL Server administration, SQL database replication


