Impact on replication when a server goes into standby mode

We have the following scenario:

Server A replicates Database A to Server B.

Server C has Database A on it as well, but in standby mode. We are applying the transaction logs generated by Database A on Server A to the database on Server C leaving it in standby mode each time.

Let's say we had planned maintenance for Server Aand dumped the last set of transactions on Server A in standby mode to be applied to to Server C. What happens to the replica on Server B? When I start to use Server C, can I backup its transactions and apply them to Server A, and then have those transactions replicated to Server B? And then what do I do when the maintenance is complete so that I can swithc back to Server A and have the replication continue on as before the maintenance to Server B?

Thanls

In SQL 2000 unless you

1) have configured Server C to also ship the master, msdb, distirbution and publication databases
2) restore the last log with the keep_replication switch
3) take Server A completely offline
4) rename ServerC to ServerA and reboot ServerC(now ServerA)
5) run sp_replrestart
6) use the continue on data consistency error profile

it will not work.

If you also follow the sequence in a failback scenario it will also work.

In SQL 2005 you can configure Server A and C as log shipping failover partners (use a remote distributor and set the publisherfailoverpartner accordingly).

Note that it is possible to do the following in SQL 2000

1) ship logs to ServerC from Server A.
2) on failover restore the tail of A to C with the keep_replication switch
3) use the sp_replrestart command to pick up where you left off

There is more potential exposure to data loss with the above method.

Impact of Changing Authentication Mode

Hi,
Our application using an SQL 2000 database, which is currently using Windows
Authentication. For some reason, we need to change the access mode to mixed
mode. Could someone please throw some light on the impact of this change.
Thanks in advance
SuhasOne extra door to guard?
Not sure what you mean by impact. From a performance or resource overhead
perspective? Nothing there. From a security perspective, you now need to
figure out how to manage the SQL Server logins to ensure they follow your
password policies (complexity, length, expiration, re-use, etc...). Not much
help built into SQL Server 2000 but in 2005, life gets a LOT better.
joe.
"Suhas Vengilat" <SuhasVengilat@.discussions.microsoft.com> wrote in message
news:34F882D9-448F-4EDC-A62C-BB87CCAF9307@.microsoft.com...
> Hi,
> Our application using an SQL 2000 database, which is currently using
> Windows
> Authentication. For some reason, we need to change the access mode to
> mixed
> mode. Could someone please throw some light on the impact of this change.
> Thanks in advance
> Suhas|||With either SQL Server 2000 or SQL Server 2005, the process is virtually
identical as follows:
Run SQL Enterprise Manager (or Start > Run > SQLwb.exe if using 2005)
Connect to the server
Launch Server Properties dialog
Switch to the Security tab
Select the Authentication option (Mixed or Windows only) > OK
Dismiss the "restart the server to implement changes" message box
"Restart" the MSSQLServer service (Start > Run > Compmgmt.msc >
services.msc)
Regards,
Keith
This posting is provided "as is" without inferring rights or warranties.
"Joe Yong" <NO_jyong_SPAM@.scalabilityexperts.com> wrote in message
news:OVSeLmxvFHA.1032@.TK2MSFTNGP12.phx.gbl...
> One extra door to guard?
> Not sure what you mean by impact. From a performance or resource overhead
> perspective? Nothing there. From a security perspective, you now need to
> figure out how to manage the SQL Server logins to ensure they follow your
> password policies (complexity, length, expiration, re-use, etc...). Not
> much help built into SQL Server 2000 but in 2005, life gets a LOT better.
>
> joe.
>
> "Suhas Vengilat" <SuhasVengilat@.discussions.microsoft.com> wrote in
> message news:34F882D9-448F-4EDC-A62C-BB87CCAF9307@.microsoft.com...
>

IIS 5.0 isolation mode

I have a Reporting Services setup on a web server on Windows 2003. It is
working fine. There is a web application that is having some problems and we
have set the web server to IIS 5.0 isolation mode. Will Reporting Services
run under 5.0 isolation mode?
At first it looks like a rights issue and giving the ASPNET account the same
rights as the NETWORK SERVICE account got us past the original access denied
type errors.
However now we are getting the error: The report server cannot decrypt the
symmetric key used to access sensitive or encrypted data in a report server
database. You must either restore a backup key or delete all encrypted
content and then restart the service.
What needs to be done to run under 5.0 isolation mode?
--
LehrSJHello,
You may want to try the following steps:
1. open C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\RSReportServer.config file.
Search for this tag, <InstallationID> and take the GUID (For example, the
GUID for me is {93850a3c-a856-4ce9-af25-6b3cdaa98dd8})
2. Use the GUID that we got before and try to remove the keys in the table
like this
RSKEYMGMT -R "{<guid>}"
3. Then run
RSACTIVATE -C "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\RSReportServer.config" > (make sure the path is the
one you installed Reporting Services)
If the issue persists, please make sure ASP.NET account has the proper
permission on the SQL server/Reprotserver databases.
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: IIS 5.0 isolation mode
| thread-index: AcVm2ZoBIp9L/GQKRtOvDPnUBn1T/g==| X-WBNR-Posting-Host: 70.118.121.7
| From: =?Utf-8?B?TGVoclNK?= <lehr524@.noemail.nospam>
| Subject: IIS 5.0 isolation mode
| Date: Wed, 1 Jun 2005 11:42:02 -0700
| Lines: 17
| Message-ID: <0021FD03-66E4-44D5-9D54-F102D1F6727F@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:45125
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| I have a Reporting Services setup on a web server on Windows 2003. It is
| working fine. There is a web application that is having some problems
and we
| have set the web server to IIS 5.0 isolation mode. Will Reporting
Services
| run under 5.0 isolation mode?
|
| At first it looks like a rights issue and giving the ASPNET account the
same
| rights as the NETWORK SERVICE account got us past the original access
denied
| type errors.
|
| However now we are getting the error: The report server cannot decrypt
the
| symmetric key used to access sensitive or encrypted data in a report
server
| database. You must either restore a backup key or delete all encrypted
| content and then restart the service.
|
| What needs to be done to run under 5.0 isolation mode?
| --
| LehrSJ
|