October 14, 2014 at 9:48 pm
We have a reporting database which is refreshed daily from prod backup and later creating new tables/views/indexes as part of the refresh job. Is there a better approach we can implement in sql 2012/2014 for this scenario since we are planning to migrate to sql2014.
Please advise.
Regards,
SQLisAwe5oMe.
October 15, 2014 at 2:26 am
Not with Availability Groups. Secondary replicas are read-only.
The new tables/views are just in the reporting database and don't need to be written back to the primary system?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 15, 2014 at 6:02 pm
Yes, correct Gail. Thanks.
Regards,
SQLisAwe5oMe.
October 16, 2014 at 2:33 am
Ok, so to confirm:
You need to be able to add views and tables to the reporting database
You don't need to change existing tables (tables from the primary)
You don't need to change data
The changes will remain local in the reporting database.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 16, 2014 at 6:53 am
Yes, correct.
Would transaction replication work for this scenario?
Regards,
SQLisAwe5oMe.
October 16, 2014 at 6:58 am
Yup, and it's about the only practical way of doing this.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply