January 25, 2008 at 4:08 pm
My application store's meta data (Server names and the application folders path etc) in one of the user table in my production database. I am building a reporting environment - which hosts different server names and has different folders path. In order to load my production database onto reporting database server - i need to change-update the production server table name first pointing to my reporting environment server names.
Here's what i have done:
Created a temp table (reflecting my meta data table) on production database.
updated this temp table to reflect my reporting server names and application folders path.
Renames this temp table to meta data table name on production.
Made a Full database backup.
Loaded this full database backup to the reporting environment server with Stand by option to have more txn file loads.
NOW: when i revert back the table name in my production environment, these changes will be send over to my stand by database and the reporting server names will be over written with the production server names on my stand by database in reporting environment. I was wondering, how can i avoid this?
Much appreciated if some one please advice here.
Many thanks,
Cali
January 25, 2008 at 5:27 pm
DTS
_____________
Donn Policarpio
January 25, 2008 at 6:04 pm
The stand by database is read only. I believe DTS wont work here.
January 25, 2008 at 7:54 pm
I meant you ditch log restore, and go with dts, otherwise, you'll get the same changes as with your source database.
_____________
Donn Policarpio
January 26, 2008 at 4:11 am
The purpose of going with logshipping was to have a automatic sync of stand by database every 30 minutes. Transfering all the accumalative changes from source to target through DTS may not with our requirement.
January 26, 2008 at 4:37 am
I'm not quite sure I follow, but it seems from reading the other comments that you have log shipping set up to keep a warm server ready for reporting... You said that the reporting database is read-only so the best solution I can think of is to change the structure of the table you're modifying to have a SERVER column. Put the data for both servers into this table at the same time using your new server column to distinguish. Then when you read the table simply add a where clause. If you cannot do that, then create a view that has the where clause = @@SERVERNAME (I cannot remember the exact name of the variable - it'll go pink in the editor when it's right. Had a couple of beers whilst watching the cricket and tennis today 😀 )
January 26, 2008 at 11:53 am
Thanks for the answer. My warm stand by environment is pointing to a different apps server and having this serve name in production table might not make any sense. Additionally the application was not developed in-house. it's a SAP application and to modify any code, have to approach SAP.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply