Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Vinnie881
Master Smack Fu Yak Hacker
1231 Posts |
 Posted - 2010-06-12 : 00:47:00
|
I have a extremly simple replication need for SQL 2005 EXPRESS (NO PUBLISH)This is all I need to do(Server 1 Local)(Server 2 Remote)I set server 2 up as a linked server.I just need to at the end of each day take 5 specific tables(NOT THE ENTIRE DATABASE) all with <50000 records and put those tables so they're accessable on a remote server.How do you suggest I do this?Thanks!
Success is 10% Intelligence, 70% Determination, and 22% Stupidity.\_/ _/ _/\_/ _/\_/ _/ _/- 881 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
Vinnie881
Master Smack Fu Yak Hacker
1231 Posts |
Posted - 2010-06-12 : 13:43:16
|
So if it was you, you would just suggest just deleting records in actable and re-inserting all records via a linked server? Do you feel there would be a benefit to using subscriber/publisher instead if I was using the non-express addition?I guess I am looking for the best method.Thanks!
Success is 10% Intelligence, 70% Determination, and 22% Stupidity.\_/ _/ _/\_/ _/\_/ _/ _/- 881 |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
Vinnie881
Master Smack Fu Yak Hacker
1231 Posts |
Posted - 2010-06-12 : 19:48:28
|
The requirments are quite simplistic. I have a public webserver which that needs to access certain records from our internal database. I do not want the internal database to be accessable via this webserver, but the only information it needs is records from about 5 differant tables (The tables I will bulk load most likely).The tables just need to be updated 1 x per day. I believe the bulk load method is the best method for me. Another related question though:I read a bunch of articles on subscriber/publisher type replication. There doesn't seem anyway to accomplish this unless both servers are accessable by each other, is this correct? Ideally I want a solution where the subscriber/receiving server can not access the SQLSERVER Instance on the publishing/source. I just want the publishing server to be able to connect to the Sucriber. It does not seem like this is a option, but with the linked server, as long as the receiving server is accessable I can publish via setting up a linked server w/o opening any security vulnerabilities (The reason I want this setup instead of setting up a VPN is the receiving server is a remote hosted Virtual Dedicated web server, and I do not want to setup a VPN since the data housed on it is not very important, so I preffer to treat it completly isoolated from everything internal with only the publishing server pushing data to it and not the webserver being able to access the internal network).Do you feel this is a good method, or should I look into something else?Thanks!!
Success is 10% Intelligence, 70% Determination, and 22% Stupidity.\_/ _/ _/\_/ _/\_/ _/ _/- 881 |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
|
|
Is there a better way to replicate this?