I have been assigned a rather large project and was looking for a little bit of expert input. Below is the assigned problem followed by the solution as I see it.
Last week I put in a T1 line at each of three locations for a local business using Cisco routers and a Sonic wall firewall per location. Their business relies on a poorly written piece of software that access's a local database using DCOM98. The problem they gave me was that a person in location A can only work on the database (MSSQL 2000) at location A, and likewise for locations B and C. With the T1 i have put each of these MSSQL servers securely on the internet with a publicly accessable IP. I have proposed linking the three databases to each other. When this is done each person at each location should be able to access each database through thier computer.
I sugested that if I create a secure connection between two of the SQL databases that any computer should be able to access any server. Logically this made sence, but when i put it into practice The clients were unable to see the remote server even though i could access from the local database's Enterprise manager. This stumped me untill i realized that the remote server was being created in an instance outside of the "default" instance. This appears to be a weakness either in the software or DCOM itself. This software also required that thier be database files stored in a specific location on the server for each database accessed. So I am once again stumped. The problem I need to solve is put less verbose below.
1 - How can i access a remote MSSQL 2000 machine remotely within the default instance of the local server?
2- How can I keep up to date copies of the database files from a remote server on the local machine?
3- And last but not least - How can I convince a large corportation to not write buggy garbage software?
Thanks and i Appreciate you time,
Micah A. Norman
Last week I put in a T1 line at each of three locations for a local business using Cisco routers and a Sonic wall firewall per location. Their business relies on a poorly written piece of software that access's a local database using DCOM98. The problem they gave me was that a person in location A can only work on the database (MSSQL 2000) at location A, and likewise for locations B and C. With the T1 i have put each of these MSSQL servers securely on the internet with a publicly accessable IP. I have proposed linking the three databases to each other. When this is done each person at each location should be able to access each database through thier computer.
I sugested that if I create a secure connection between two of the SQL databases that any computer should be able to access any server. Logically this made sence, but when i put it into practice The clients were unable to see the remote server even though i could access from the local database's Enterprise manager. This stumped me untill i realized that the remote server was being created in an instance outside of the "default" instance. This appears to be a weakness either in the software or DCOM itself. This software also required that thier be database files stored in a specific location on the server for each database accessed. So I am once again stumped. The problem I need to solve is put less verbose below.
1 - How can i access a remote MSSQL 2000 machine remotely within the default instance of the local server?
2- How can I keep up to date copies of the database files from a remote server on the local machine?
3- And last but not least - How can I convince a large corportation to not write buggy garbage software?
Thanks and i Appreciate you time,
Micah A. Norman
