|
|
You're in the
sql server replication
group:Table access privileges
sql server replication:
this is more of a request to get the questions I need, rather than the answers. I received the following email this morning: It looks that we had restarted the replication recently that seemed to have reset some of the table access privileges. I have reset those so that you can have access to all of the tables in EDI database. Sorry for the trouble. When I asked what type of replication it is, I got both: "transactional" and Publisher/Subscriber (definitely not Log Shipping, the only one I know). I also know that the source (publisher?) system had recently had new tables added and that the final destination system had permission reset on more tables than just the new ones. SQL Server 2000 on all machines. The architecture is: Source1 (active/passive cluster) --\ Source2 ---> ProRep (some kind of staging server) -> CorpRep (where the data is used) Source3 --/ What information do I need to get before I can even begin this process? Thanks, Jay
Thank you. Three questions:
1) Where do I find the entry point for the "post snapshot script"? 2) Is there a reasonable way to grant security at a higher level that wouldn't require re-applying them? 3) Why does it only happen when new tables are added and not every time the database is replicated? [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:uLLBt504HHA.5212@TK2MSFTNGP04.phx.gbl... > What probably happened was that you have object level security on the > replicated tables, i.e. through grant statements. When the tables are > dropped when the snapshot is applied these grant statements are wiped out. > You would need to re-apply them as part of a post snapshot script. > > -- > relevantNoise - dedicated to mining blogs for business intelligence. > > 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 > "Jay" <nospam@nospam.org> wrote in message > news:OquG0a04HHA.556@TK2MSFTNGP06.phx.gbl... >> I'm not super familiar with all of the forms of SQL Server replication, >> so this is more of a request to get the questions I need, rather than the >> answers. >> >> I received the following email this morning: >> >> It looks that we had restarted the replication recently that >> seemed to have reset some >> of the table access privileges. I have reset those so that you can >> have access to all >> of the tables in EDI database. Sorry for the trouble. >> >> When I asked what type of replication it is, I got both: "transactional" >> and Publisher/Subscriber (definitely not Log Shipping, the only one I >> know). >> I also know that the source (publisher?) system had recently had new >> tables added and that the final destination system had permission reset >> on more tables than just the new ones. >> SQL Server 2000 on all machines. >> The architecture is: >> Source1 (active/passive cluster) --\ >> Source2 ---> ProRep (some kind of >> staging server) -> CorpRep (where the data is used) >> Source3 --/ >> >> What information do I need to get before I can even begin this process? >> >> Thanks, >> Jay >> > >
What probably happened was that you have object level security on the
replicated tables, i.e. through grant statements. When the tables are dropped when the snapshot is applied these grant statements are wiped out. You would need to re-apply them as part of a post snapshot script. -- relevantNoise - dedicated to mining blogs for business intelligence. 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 [quoted text, click to view] "Jay" <nospam@nospam.org> wrote in message news:OquG0a04HHA.556@TK2MSFTNGP06.phx.gbl... > I'm not super familiar with all of the forms of SQL Server replication, so > this is more of a request to get the questions I need, rather than the > answers. > > I received the following email this morning: > > It looks that we had restarted the replication recently that seemed > to have reset some > of the table access privileges. I have reset those so that you can > have access to all > of the tables in EDI database. Sorry for the trouble. > > When I asked what type of replication it is, I got both: "transactional" > and Publisher/Subscriber (definitely not Log Shipping, the only one I > know). > I also know that the source (publisher?) system had recently had new > tables added and that the final destination system had permission reset on > more tables than just the new ones. > SQL Server 2000 on all machines. > The architecture is: > Source1 (active/passive cluster) --\ > Source2 ---> ProRep (some kind of > staging server) -> CorpRep (where the data is used) > Source3 --/ > > What information do I need to get before I can even begin this process? > > Thanks, > Jay >
1) right click on your publication and select properties, then select the
snapshot tab, in the additional scripts section enter the post snapshot script in the After applying the snapshot, execute this script dialog box. 2) roles will probably work. 3) because when new tables are added the existing ones with the same name on the subscriber are dropped. When they are dropped the permissions applied to them are lost. -- relevantNoise - dedicated to mining blogs for business intelligence. 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 [quoted text, click to view] "Jay" <nospam@nospam.org> wrote in message news:ua0EsF14HHA.5424@TK2MSFTNGP02.phx.gbl... > Thank you. Three questions: > > 1) Where do I find the entry point for the "post snapshot script"? > 2) Is there a reasonable way to grant security at a higher level that > wouldn't require re-applying them? > 3) Why does it only happen when new tables are added and not every time > the database is replicated? > > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:uLLBt504HHA.5212@TK2MSFTNGP04.phx.gbl... >> What probably happened was that you have object level security on the >> replicated tables, i.e. through grant statements. When the tables are >> dropped when the snapshot is applied these grant statements are wiped >> out. You would need to re-apply them as part of a post snapshot script. >> >> -- >> relevantNoise - dedicated to mining blogs for business intelligence. >> >> 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 >> "Jay" <nospam@nospam.org> wrote in message >> news:OquG0a04HHA.556@TK2MSFTNGP06.phx.gbl... >>> I'm not super familiar with all of the forms of SQL Server replication, >>> so this is more of a request to get the questions I need, rather than >>> the answers. >>> >>> I received the following email this morning: >>> >>> It looks that we had restarted the replication recently that >>> seemed to have reset some >>> of the table access privileges. I have reset those so that you >>> can have access to all >>> of the tables in EDI database. Sorry for the trouble. >>> >>> When I asked what type of replication it is, I got both: "transactional" >>> and Publisher/Subscriber (definitely not Log Shipping, the only one I >>> know). >>> I also know that the source (publisher?) system had recently had new >>> tables added and that the final destination system had permission reset >>> on more tables than just the new ones. >>> SQL Server 2000 on all machines. >>> The architecture is: >>> Source1 (active/passive cluster) --\ >>> Source2 ---> ProRep (some kind of >>> staging server) -> CorpRep (where the data is used) >>> Source3 --/ >>> >>> What information do I need to get before I can even begin this process? >>> >>> Thanks, >>> Jay >>> >> >> > >
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |