November 2, 2011 at 1:17 pm
Hello to the forums btw. Here's where I'm stuck on a whole scenario, and the scenario goes like this:
I've a home brewed production database for invoicing and the such. What I wanted was a copy of the database for Reporting. I tried the replication on transaction level but you need prime keys to do so none of the tables have them. So I went down the path of log shipping but now I see every time it restores the log to the secondary db it needs sole access to the secondary db to do so. Well this posed me into a thought that i could just some how use my secondary db and put it in as a reporting database in some sort of manner, but that is where I fail to find any info on to point me in any direction that way. So the question is that the way I should go about it or do something differently?
I work for a place where it's very fast pace and small amount of time to get anything done so just copying the prod db and setting up a main place for queries in a central location for reporting will work fine to shift thoughts and eyes upon the capability of this resource is all I'm trying to get at. Thanks for any input and again hello to All in the SQLSeverCentral forums.
November 2, 2011 at 11:52 pm
If you decided about log-shipping then you can modify your log restore script with two option :-
1) you can delay the log restore by "n" minutes if users are connected. Now the value of "n" depends on how much recent data you need.
2) After "n" minutes passed, force the active connection to be killed and restore all the pending log
----------
Ashish
November 3, 2011 at 11:14 am
That's something cool to know and I will use, but how do I take that DB and put it into my reporting services? Or am I being stupid or too much to answer for that question?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply