April 15, 2003 at 2:42 am
This is a "normal" situation.
You start with 1 database(s) on 1 machine and then 2,3,4,... Now you want to move a database to another machine. Of course as clean and simple as possible.
Database db-A shares data to many others. Database db-B has to move but has a lot of references to db-A.
If I'll use a linked server I have to modify the T-SQL in dbB (replacing "db-A" by "ServerA.db-A"). Right?
If I could use a linked database I do not have to modify anything at all.
Is this possible?
April 15, 2003 at 5:56 am
Couple different ways you could do it. One would be to replicate the one db back, using either merge or transactional with updates. The other is once you move the db, create an empty db with the same name on the original server. Create the linked server. Create one view per table named exactly what the table was named (no v~ prefix) using the linked server. Grant any permissions needed on the views. Or if you were using views exclusively earlier, you can just modify them.
Andy
April 17, 2003 at 8:41 am
I am sure someone else has resolved this issue and can add information to avoid the problems we experienced. When we started to query across machines (using SQL Standard), even in read-only, nolock queries, performance was abysmal. If we accessed the data through stored procedures, the performance was stored.
Are there options other than using SQL Enterprise to efficiently query across machines?
Guarddata-
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply