June 4, 2008 at 3:16 pm
I have a production database on SQL Server 2000 that is being constantly hit by reports, I want to create a reporting server and so far I think my options are log shipping to another SS 2000 server but I don't like the idea that no users are allowed during the log restore on the secondary server, also there's replication but this database is about 70GB and I need to replicate all tables for the reports, I'm not sure this is a good option.
Is there any other way or an easy way to do this?
I also have a SQL server 2005 doing nothing, is there any feature in 2005 that I can take advantage of for creating my reporting database?
thx.
June 4, 2008 at 8:04 pm
Do you need real time data? If not, you can set a delay on log shipping to only sync after business hours. That way the database will be online all day for reporting and you will not have to kick users off for a restore. Many times in reporting environments running a day behind is ok.
June 5, 2008 at 9:03 am
Thanks for the reply. The data doesn't have to be real time but during the last 10 days of the month it has to be not older than 1-2 hours max and the amount of reports requested during those days is high. Perhaps the rest of the month we can live with one update a day after regular business hours.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply