Database replication

Hi,

Wondering if anyone can help. We have a knowledge base system which uses an
MSSQL server to store information. The tool is web-based, and we have need
to run reports on the information in the database, such as number and age of
articles, for example.

As the tool is used quite heavily, we can't afford the drop in performance
that reporting on the live database would cause, so we have setup another
database server which is to hold a copy of the database.

We have a job set up in Enterprise Administrator which takes a backup of the
database from the live server every night and copies it over to the
reporting server. A job on the reporting server then restores the copy from
the live server over the top.

However, the job on the reporting server consistently fails when it is run.
It appears as though the database file on the reporting server is becoming
unusable, however the copy remaining on the live server is fine.

We are able to restore the database by manually copying over the file,
however this takes up valuable DBA time that could be better used
elsewhere - has anyone else ever experienced anything like this, and if so
how did you get round it?

The database backup file is around 3.5GB in size.

Cheers,

Andi

Re: Database replication

On Sep 4, 10:50 pm, "Andi" wrote:
> Hi,
>
> Wondering if anyone can help. We have a knowledge base system which uses an
> MSSQL server to store information. The tool is web-based, and we have need
> to run reports on the information in the database, such as number and age of
> articles, for example.
>
> As the tool is used quite heavily, we can't afford the drop in performance
> that reporting on the live database would cause, so we have setup another
> database server which is to hold a copy of the database.
>
> We have a job set up in Enterprise Administrator which takes a backup of the
> database from the live server every night and copies it over to the
> reporting server. A job on the reporting server then restores the copy from
> the live server over the top.
>
> However, the job on the reporting server consistently fails when it is run.
> It appears as though the database file on the reporting server is becoming
> unusable, however the copy remaining on the live server is fine.
>
> We are able to restore the database by manually copying over the file,
> however this takes up valuable DBA time that could be better used
> elsewhere - has anyone else ever experienced anything like this, and if so
> how did you get round it?
>
> The database backup file is around 3.5GB in size.
>
> Cheers,
>
> Andi

Which version of sql server you are using ?

For the above requirement log shipping (if destination is for read
only purpose) or transactional replciation can be usefull

you can refere books online for setp info

Let me know if anything needed on this

Thanks
Vijayasekar