Feedback on design issue sought

First, a brief backgrounder . . . I work for a small but quickly
growing company with a voracious appetite for data but limited
resources to provide the infrastructure I think they need to supply
this data.
The problem . . . Our primary operations application data, which
represents much of the data employees would like to access for various
reporting needs, is hosted in an off-site SQL Server 2005 database. I
would like to provide local access to this data so that A) people
aren't reporting off of a production operations database and B) we
don't have to worry about VPN's, network issues, etc. My understanding
is that I cannot mirror a 2005 database to a 2000 database. Is this
correct? If so, does anyone have suggestions for an alternative
approach to the problem? I could do some hokey thing with scripts and
scheduled tasks and move the nightly bak file around and restore it
using DTS or something like that, but I was thinking there must be a
more elegant way to address the issue.
Any thoughts? 24 hour latency of the data is acceptable.
Thanks,
Rich
You can only mirror from SQL 2005 to SQL 2005 servers.
You might be able to use replication for this depending on what ports are
open on your respective firewalls, or you could also use log shipping and
send the logs and backup via ftp. DTS is another option.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rich" <rsbaier@.gmail.com> wrote in message
news:1161110521.900413.111550@.k70g2000cwa.googlegr oups.com...
> First, a brief backgrounder . . . I work for a small but quickly
> growing company with a voracious appetite for data but limited
> resources to provide the infrastructure I think they need to supply
> this data.
> The problem . . . Our primary operations application data, which
> represents much of the data employees would like to access for various
> reporting needs, is hosted in an off-site SQL Server 2005 database. I
> would like to provide local access to this data so that A) people
> aren't reporting off of a production operations database and B) we
> don't have to worry about VPN's, network issues, etc. My understanding
> is that I cannot mirror a 2005 database to a 2000 database. Is this
> correct? If so, does anyone have suggestions for an alternative
> approach to the problem? I could do some hokey thing with scripts and
> scheduled tasks and move the nightly bak file around and restore it
> using DTS or something like that, but I was thinking there must be a
> more elegant way to address the issue.
> Any thoughts? 24 hour latency of the data is acceptable.
> Thanks,
> Rich
>
|||On 17 Oct 2006 11:42:01 -0700, "Rich" <rsbaier@.gmail.com> wrote:
>Any thoughts? 24 hour latency of the data is acceptable.
Go with the .bak file.
J.
|||Log Shipping could be a good solution for your situation.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Rich" <rsbaier@.gmail.com> wrote in message
news:1161110521.900413.111550@.k70g2000cwa.googlegr oups.com...
> First, a brief backgrounder . . . I work for a small but quickly
> growing company with a voracious appetite for data but limited
> resources to provide the infrastructure I think they need to supply
> this data.
> The problem . . . Our primary operations application data, which
> represents much of the data employees would like to access for various
> reporting needs, is hosted in an off-site SQL Server 2005 database. I
> would like to provide local access to this data so that A) people
> aren't reporting off of a production operations database and B) we
> don't have to worry about VPN's, network issues, etc. My understanding
> is that I cannot mirror a 2005 database to a 2000 database. Is this
> correct? If so, does anyone have suggestions for an alternative
> approach to the problem? I could do some hokey thing with scripts and
> scheduled tasks and move the nightly bak file around and restore it
> using DTS or something like that, but I was thinking there must be a
> more elegant way to address the issue.
> Any thoughts? 24 hour latency of the data is acceptable.
> Thanks,
> Rich
>