Getting a database on one server to match another

Sorry wasn't too clear was I.
The second server is our disaster recovery server, so we
want our second server database to be as up to date as
possible with the production database.
ta

>--Original Message--
>Hello,
>We have two servers and want out production db on server
1
>to match the production server on server 2.
>Whats the best way of doing this?
>.
>Sarah,
Hari already answered this with:
1) Log Shipping
2) Transactional replication
If the disaster recovery server does not need to be operational, then log
shipping would be good.You may also want to consider Double-Take from NSI
Software. This replicates the SQL Server data files at the block level on
disk and ensures transactional consistency.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:4c5401c42c3a$23ff0f60$a001280a@.phx.gbl...[vbcol=seagreen]
> Sorry wasn't too clear was I.
> The second server is our disaster recovery server, so we
> want our second server database to be as up to date as
> possible with the production database.
> ta
>
> 1|||Thanks Mark,
I'll have a look at transactional replication as we backup
the Production db by log files and to be honest I'm not
too sure on what will happen if we change it so it updates
asap.
Thanks for your time

>--Original Message--
>Sarah,
>Hari already answered this with:
>1) Log Shipping
>2) Transactional replication
>If the disaster recovery server does not need to be
operational, then log
>shipping would be good.You may also want to consider
Double-Take from NSI
>Software. This replicates the SQL Server data files at
the block level on
>disk and ensures transactional consistency.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>
>
>"Sarah" <anonymous@.discussions.microsoft.com> wrote in
message
>news:4c5401c42c3a$23ff0f60$a001280a@.phx.gbl...
server[vbcol=seagreen]
>
>.
>|||There's a web site at MS called something like "Pattern and practices". Ther
e you find a two boos on SQL
Server and high availability. You really need to go through that if you inte
nd to use replication for fail
over. There are some issues you need to plan for.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Sarah" <anonymous@.discussions.microsoft.com> wrote in message news:4ae801c42c41$337182f0$a4
01280a@.phx.gbl...[vbcol=seagreen]
> Thanks Mark,
> I'll have a look at transactional replication as we backup
> the Production db by log files and to be honest I'm not
> too sure on what will happen if we change it so it updates
> asap.
> Thanks for your time
>
>
> operational, then log
> Double-Take from NSI
> the block level on
> message
> server|||Sarah,
I really don't think transactional replication is a good high availability
solution. There are many drawbacks to using this. Do a search on the web for
high availability sql server and you should find some good information.
Kimberley Tripp did a great presentation on high availability, perhaps
search for that.
Log shipping might be a good way to go, you can have a latency of 5 minutes
with this solution.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:4ae801c42c41$337182f0$a401280a@.phx.gbl...[vbcol=seagreen]
> Thanks Mark,
> I'll have a look at transactional replication as we backup
> the Production db by log files and to be honest I'm not
> too sure on what will happen if we change it so it updates
> asap.
> Thanks for your time
>
>
> operational, then log
> Double-Take from NSI
> the block level on
> message
> server|||Thanks for your help guys

>--Original Message--
>Thanks Mark,
>I'll have a look at transactional replication as we
backup
>the Production db by log files and to be honest I'm not
>too sure on what will happen if we change it so it
updates
>asap.
>Thanks for your time
>
>
>operational, then log
>Double-Take from NSI
>the block level on
>message
we[vbcol=seagreen]
>server
>.
>

Getting a database on one server to match another

Sorry wasn't too clear was I.
The second server is our disaster recovery server, so we
want our second server database to be as up to date as
possible with the production database.
ta

>--Original Message--
>Hello,
>We have two servers and want out production db on server
1
>to match the production server on server 2.
>Whats the best way of doing this?
>.
>
Sarah,
Hari already answered this with:
1) Log Shipping
2) Transactional replication
If the disaster recovery server does not need to be operational, then log
shipping would be good.You may also want to consider Double-Take from NSI
Software. This replicates the SQL Server data files at the block level on
disk and ensures transactional consistency.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:4c5401c42c3a$23ff0f60$a001280a@.phx.gbl...[vbcol=seagreen]
> Sorry wasn't too clear was I.
> The second server is our disaster recovery server, so we
> want our second server database to be as up to date as
> possible with the production database.
> ta
>
> 1
|||Thanks Mark,
I'll have a look at transactional replication as we backup
the Production db by log files and to be honest I'm not
too sure on what will happen if we change it so it updates
asap.
Thanks for your time

>--Original Message--
>Sarah,
>Hari already answered this with:
>1) Log Shipping
>2) Transactional replication
>If the disaster recovery server does not need to be
operational, then log
>shipping would be good.You may also want to consider
Double-Take from NSI
>Software. This replicates the SQL Server data files at
the block level on
>disk and ensures transactional consistency.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>
>
>"Sarah" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:4c5401c42c3a$23ff0f60$a001280a@.phx.gbl...
server
>
>.
>
|||There's a web site at MS called something like "Pattern and practices". There you find a two boos on SQL
Server and high availability. You really need to go through that if you intend to use replication for fail
over. There are some issues you need to plan for.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Sarah" <anonymous@.discussions.microsoft.com> wrote in message news:4ae801c42c41$337182f0$a401280a@.phx.gbl...[vbcol=seagreen]
> Thanks Mark,
> I'll have a look at transactional replication as we backup
> the Production db by log files and to be honest I'm not
> too sure on what will happen if we change it so it updates
> asap.
> Thanks for your time
>
>
> operational, then log
> Double-Take from NSI
> the block level on
> message
> server
|||Sarah,
I really don't think transactional replication is a good high availability
solution. There are many drawbacks to using this. Do a search on the web for
high availability sql server and you should find some good information.
Kimberley Tripp did a great presentation on high availability, perhaps
search for that.
Log shipping might be a good way to go, you can have a latency of 5 minutes
with this solution.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:4ae801c42c41$337182f0$a401280a@.phx.gbl...[vbcol=seagreen]
> Thanks Mark,
> I'll have a look at transactional replication as we backup
> the Production db by log files and to be honest I'm not
> too sure on what will happen if we change it so it updates
> asap.
> Thanks for your time
>
>
> operational, then log
> Double-Take from NSI
> the block level on
> message
> server
|||Thanks for your help guys

>--Original Message--
>Thanks Mark,
>I'll have a look at transactional replication as we
backup
>the Production db by log files and to be honest I'm not
>too sure on what will happen if we change it so it
updates[vbcol=seagreen]
>asap.
>Thanks for your time
>
>
>operational, then log
>Double-Take from NSI
>the block level on
>message
we
>server
>.
>
sql

Get report server functional is not very clear could someone explain the security requirements?

We have reports server installed using the local system account when we try to access through web browrse we get and error that say that we need to go to the local system and view the event log. In the system event log there are lots of error that are complaining about dcom object not having permission and in the application log we are getting errors also I have tried to find some documentation that explains the set up requirements and have found lots of disconnect documents that do not give a good explanation of how to setup the accounts needed. I have been able to develop some very nice reports use BI studio but can seem to deploy them and we are unable to use report builder. Any help would be greatly apprecaited.. How do we get this enviroment correct...? When report server was installed it was installed using the local account and with the all other defaults. I'm sure that the issue is some sort of security problem but have no idea what I have to do get past this problem.. Also can you point me to a document that has the minium account requirments to be able to run this service? Or any other documentation that may be more complete and less fragmented that online books..

SQL server was installed using mixed security.

Is there a good book that explains this stuff?

I would try opening the Reporing Services Configuration Manager in the Windows Service Identity tab, and change the authentication to either a local windows domain account or an active directory domain account. Then try again and see what happens.|||I still get the following error

EventType sql90exception, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435be1, P4 reportingservicesnativeclient.ni.dll, P5 2005.90.1399.0, P6 43e29533, P7 0, P8 00005253, P9 00000000, P10 NIL.

|||I don't really know where to go from there. If you have all components running on your local server (SQL 2005, Reporting Services, IIS), I would think using a local Administrator account should work, and then you could back off from there to lower security once you have it working. Maybe it isn't a security issue. Sorry I couldn't be more help.|||

Hello,

I've same error as your's, but before ReportServer works fine and now after changind IP adress I get an error

EventType sql90exception, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435be1, P4 reportingservicesnativeclient.ni.dll, P5 2005.90.1399.0, P6 443ccc82, P7 ...

No solution, I search !!!!

Do you solve your problem ?

Get report server functional is not very clear could someone explain the security requiremen

We have reports server installed using the local system account when we try to access through web browrse we get and error that say that we need to go to the local system and view the event log. In the system event log there are lots of error that are complaining about dcom object not having permission and in the application log we are getting errors also I have tried to find some documentation that explains the set up requirements and have found lots of disconnect documents that do not give a good explanation of how to setup the accounts needed. I have been able to develop some very nice reports use BI studio but can seem to deploy them and we are unable to use report builder. Any help would be greatly apprecaited.. How do we get this enviroment correct...? When report server was installed it was installed using the local account and with the all other defaults. I'm sure that the issue is some sort of security problem but have no idea what I have to do get past this problem.. Also can you point me to a document that has the minium account requirments to be able to run this service? Or any other documentation that may be more complete and less fragmented that online books..

SQL server was installed using mixed security.

Is there a good book that explains this stuff?

I would try opening the Reporing Services Configuration Manager in the Windows Service Identity tab, and change the authentication to either a local windows domain account or an active directory domain account. Then try again and see what happens.|||I still get the following error

EventType sql90exception, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435be1, P4 reportingservicesnativeclient.ni.dll, P5 2005.90.1399.0, P6 43e29533, P7 0, P8 00005253, P9 00000000, P10 NIL.

|||I don't really know where to go from there. If you have all components running on your local server (SQL 2005, Reporting Services, IIS), I would think using a local Administrator account should work, and then you could back off from there to lower security once you have it working. Maybe it isn't a security issue. Sorry I couldn't be more help.|||

Hello,

I've same error as your's, but before ReportServer works fine and now after changind IP adress I get an error

EventType sql90exception, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435be1, P4 reportingservicesnativeclient.ni.dll, P5 2005.90.1399.0, P6 443ccc82, P7 ...

No solution, I search !!!!

Do you solve your problem ?