Applying SP4 on Replicated databases

Hi,
We have transactional replication with 30 subscribers. We are planning to
upgrade to sp4 from sp3a. Publisher and distributor are in the same server.
So is there any order(sequence) like first we have to upgrade publisher and
then subscriber...
Is there any known issues/impact on publisher or subscriber.
Thanks in advance for your help.
Thanks
Prabhu
The rule is
Local Distributor - upgrade the publisher/distributor first then the
subscribers
Remote Distributor - upgrade the distributor, then the publisher, and
finally the subscriber(s).
"Prabhu" <Prabhu@.discussions.microsoft.com> wrote in message
news:B7770777-C2B2-4E30-9F13-354A18A3666E@.microsoft.com...
> Hi,
> We have transactional replication with 30 subscribers. We are planning to
> upgrade to sp4 from sp3a. Publisher and distributor are in the same
> server.
> So is there any order(sequence) like first we have to upgrade publisher
> and
> then subscriber...
> Is there any known issues/impact on publisher or subscriber.
> Thanks in advance for your help.
> Thanks
> Prabhu
>
|||Thanks cotter,
So we don't need to worry about the subscriber type, whether its read-only
or updatable subscriber. Am i right ? or is there any difference for these
types.
Thanks
Prabhu
"Hilary Cotter" wrote:

> The rule is
> Local Distributor - upgrade the publisher/distributor first then the
> subscribers
> Remote Distributor - upgrade the distributor, then the publisher, and
> finally the subscriber(s).
> "Prabhu" <Prabhu@.discussions.microsoft.com> wrote in message
> news:B7770777-C2B2-4E30-9F13-354A18A3666E@.microsoft.com...
>
>
|||Yes you don't have to worry about the subscribers. Just do them last.
I always shut down the SQL Server agents on the boxes before doing the
upgrades. You will need to notify your users that you are doing upgrades so
you can kick them off.
Hilary
"Prabhu" <Prabhu@.discussions.microsoft.com> wrote in message
news:EC578700-3B73-4C38-9255-4FA97C79A7B4@.microsoft.com...[vbcol=seagreen]
> Thanks cotter,
> So we don't need to worry about the subscriber type, whether its
> read-only
> or updatable subscriber. Am i right ? or is there any difference for these
> types.
> Thanks
> Prabhu
>
>
> "Hilary Cotter" wrote:

Applying ASP.NET 2.0 to custom pages

Ok I already have a database layed out with several tables and relationships set up, and i went ahead and built a bunch of pages that I was planning on using. While i was doing this I ran into 2 problems, the first was i wrote some SQL statements to insert data from input boxes into some tables i have in my database, i used a catch exception statement as well as a if/else statement to handle the transfer to diffirent pages like a signup succeded or failed, the problem im having is that the data isnt saving into the database. (I was modeling my code after the Video 8 in the Learning SQL server 2005 Express Edition for Beginners Video Series.... I actually got them to work......sorta....) When i test it no exceptions are thrown and it continues on like nothing went wrong. The other Problem i ran into was i realized i wanted to use the memberships and roles provided by ASP.NET 2.0, and since i already created the pages for the site, i was wondering if there was a way to add them in. This site isnt anything fancy at all, i wanted to try and create a app where users sign up and create an account on the site, but i also wanted to have the flexability to insert and retrieve data from the database with out having to be stuck in the templates. Sorry for the long story im trying to give all the info possible. Any help on this would be great! Thanks!

I can understand were you are, but you might get a better answer posting on http://forums.asp.net in the security and membership groups as well as the data access group. Most of the problems or methods that you are describing are general and not just related to SQL Express.

Here is a quick link to Building a simple login system using the asp.net 2.0 login controls in 24 lines of code.

Here is a simple tutorial on Building a simple data layer that might assist your project.

Apply snapshot regularly

I am planning to do a snapshot regularly once a month to make sure that the
publshing database and subscriber database are always in sycn. Our system
is 24x7 but night time and weekend are relatively quiet. Is the correct
process for this is to do the 'Reinitialize All subscriptions' in Replication
Monitor or just start the Snapshot Agents? Do I need to shut down the
Distribution Agent and/or Log Reader Agent first before I do anyone of these
options?
Also, will the tables in the publishing database that are being transferred
over to the subscribing server be locked by SQL server during the transfer?
wingman
There is no point to do this unless you know you are out of sync. I would
run monthly or weekly validations to see if you are out of sync. Then if you
are reinitialize and then manually start the snapshot agent. The log reader
and distribution agents run fine when you are simultaneously generating a
snapshot.
For named subscriptions the snapshot will only be generated when you have a
new subscription, or when you have reinitialized a subscription or
subscriptions. For anonymous subscriptions a snapshot will be run each time
your snapshot agent runs.
While the snapshot agent is being run the published tables will be locked.
After the snapshot has finished the locks will be released, while the
distribution and log reader agents are running they will not hold any locks
on the published tables.
Hilary Cotter
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
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:B03834F3-CA1F-4CC8-9A79-E59593C3CD33@.microsoft.com...
>I am planning to do a snapshot regularly once a month to make sure that the
> publshing database and subscriber database are always in sycn. Our
> system
> is 24x7 but night time and weekend are relatively quiet. Is the correct
> process for this is to do the 'Reinitialize All subscriptions' in
> Replication
> Monitor or just start the Snapshot Agents? Do I need to shut down the
> Distribution Agent and/or Log Reader Agent first before I do anyone of
> these
> options?
> Also, will the tables in the publishing database that are being
> transferred
> over to the subscribing server be locked by SQL server during the
> transfer?
> wingman
|||Thanks for the great detail. I appreciate that a lot. Just one quick
follow-up question, say I only have one subscription, what is the difference
between 'reinitialize all subscriptions' and running the 'snapshot' again?
Wing
"Hilary Cotter" wrote:

> There is no point to do this unless you know you are out of sync. I would
> run monthly or weekly validations to see if you are out of sync. Then if you
> are reinitialize and then manually start the snapshot agent. The log reader
> and distribution agents run fine when you are simultaneously generating a
> snapshot.
> For named subscriptions the snapshot will only be generated when you have a
> new subscription, or when you have reinitialized a subscription or
> subscriptions. For anonymous subscriptions a snapshot will be run each time
> your snapshot agent runs.
> While the snapshot agent is being run the published tables will be locked.
> After the snapshot has finished the locks will be released, while the
> distribution and log reader agents are running they will not hold any locks
> on the published tables.
>
> --
> Hilary Cotter
> 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
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:B03834F3-CA1F-4CC8-9A79-E59593C3CD33@.microsoft.com...
>
>
|||If you run the snapshot again the snapshot will only be generated if there
is a subscription that needs it or if you are using anonymous subscriptions.
Note that if you are using anonymous subscribers the snapshot will be
generated but not sent (unless a subscriber needs one which occurs in two
cases - it does not yet have a snapshot, or if you have reinitialized this
subscriptions or all subscriptions)
if you reinitialize all subscriptions, a snapshot will be generated the next
time your snapshot agent runs and be distributed to all of your subscribers.
So reinitialize is saying this subscriber(s) needs a new snapshot and the
snapshot will be generated the next time the snapshot agent runs, running
the snapshot agent merely will generate a snapshot if someone needs it for
named, or every time for anonymous.
Hope this makes sense - its a difficult concept to understand.
Hilary Cotter
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
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:9E592EC9-CB21-41CD-A274-4FEE79AA940A@.microsoft.com...[vbcol=seagreen]
> Thanks for the great detail. I appreciate that a lot. Just one quick
> follow-up question, say I only have one subscription, what is the
> difference
> between 'reinitialize all subscriptions' and running the 'snapshot' again?
> Wing
> "Hilary Cotter" wrote:
|||Thanks!! I got it now.
"Wingman" wrote:

> I am planning to do a snapshot regularly once a month to make sure that the
> publshing database and subscriber database are always in sycn. Our system
> is 24x7 but night time and weekend are relatively quiet. Is the correct
> process for this is to do the 'Reinitialize All subscriptions' in Replication
> Monitor or just start the Snapshot Agents? Do I need to shut down the
> Distribution Agent and/or Log Reader Agent first before I do anyone of these
> options?
> Also, will the tables in the publishing database that are being transferred
> over to the subscribing server be locked by SQL server during the transfer?
> wingman