March 21, 2012 at 1:55 pm
Hello Friends, I was wondering if you can help me finding a solution....We need to extract data on a daily basis from production database but since this is production we don’t want to use it for this purpose so we thought of setting up Mirroring and creating snapshot and extract it from there but again because of too many transactions going through the database mirroring is not the option since Mirroring is good for low transaction database. We don’t want to use logship since we don’t want to wait for log restore on the secondary server. Now the question is..what are my options to achieve this in SQL? Please help
March 21, 2012 at 3:48 pm
Before we go down that path why don't you explain why you don't want to do this from your prod box? Are these big extracts? Why don't you tell us a little bit more about those first. Then we can help guide to a solution.
CEWII
March 22, 2012 at 7:53 am
Thank you for your response. Well. basically they will be pulling data from SQL and putting into DB2 so we were planning to create a replica of that prod sql db since we don’t want to hurt production performance and it is going to be a very heavy transactional db so Mirroring is out of question...that’s why i was looking for some advice on how to accomplish this
March 22, 2012 at 8:50 am
Curious why you think mirroring using a snapshot db to create a static point in time version wouldn't work? Have you done any testing?
March 23, 2012 at 6:52 am
Two questions:
1- How big is your SQL Server database?
2- Do you need near-real-time extracts to DB2 or a daily snapshot would suffice?
Depending on answers I would consider either restoring a production backup as "reporting" or go for transactional replication.
Last but not least... what do you consider "heavy transactional database"?
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.March 23, 2012 at 6:54 am
sqlquest2575 (3/21/2012)
Hello Friends, I was wondering if you can help me finding a solution....We need to extract data on a daily basis from production database but since this is production we don’t want to use it for this purpose so we thought of setting up Mirroring and creating snapshot and extract it from there but again because of too many transactions going through the database mirroring is not the option since Mirroring is good for low transaction database. We don’t want to use logship since we don’t want to wait for log restore on the secondary server. Now the question is..what are my options to achieve this in SQL? Please help
You cannot possibly expect a forum thread to get you where you need to be. You will absolutely need to get professional help to be able to a) REALLY understand what your needs truly are and b) get the proper option chosen for your particular nuances and needs and c) get it properly implemented, maintained, monitored, etc.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
March 23, 2012 at 8:21 pm
Well..SQLGuru..first of all i would like to thank everyone who responded to my question and secondly..i was just trying to get some expert advice and was not trying to waste anyone's time here . It looks like you took it personally....
March 24, 2012 at 8:07 am
sqlquest2575 (3/23/2012)
Well..SQLGuru..first of all i would like to thank everyone who responded to my question and secondly..i was just trying to get some expert advice and was not trying to waste anyone's time here . It looks like you took it personally....
Not at all! I was simply giving you the best advice I could give for your post - just like I do for every post I reply to. Forum posts are REALLY good for short/quick/targeted issues, usually involving sample data/schemas and expected outcomes. Outside of those parameters they fall down quickly. I have seen people try for weeks to get very complicated scenarios described and fleshed out and addressed. At best it almost always leaves those involved feeling frustrated and unsatisfied - at worst posters go off and do unfortunate things because details were missed, misrepresented, etc.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
May 14, 2012 at 1:12 am
mirroring or transactional replication could be possible solution here but first database size and transaction frequency should be revealed here.
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply