Hi Guys,
i am planning to implement logshipping in sql 2000 which
is already a pulisher for transactional replication.
i am planning to take transaction log backup in the
interval of 1(one) minute.
if network connection broken will it affect restoring at
desination server?
can i make the share for transaction log backup folder on
network instead of production server?
overall will it have any negative impacton source server.
Pls advice
Thanks
Biju
Biju,
although the graphical interface doesn't implement the option to backup to a different computer (in terms of browsing), you can use a network share by typing it in. I haven't done this in anger before but I guess the usual constraints of bandwidth, networ
k useage etc would obviously apply.
Regards,
Paul Ibison
Showing posts with label replication. Show all posts
Showing posts with label replication. Show all posts
Friday, March 23, 2012
logshipping question
Hi Guys,
i am planning to implement logshipping in sql 2000 which
is already a pulisher for transactional replication.
i am planning to take transaction log backup in the
interval of 1(one) minute.
if network connection broken will it affect restoring at
desination server?
can i make the share for transaction log backup folder on
network instead of production server?
overall will it have any negative impacton source server.
Pls advice
Thanks
Biju
1. Don't try to do log shipping at an interval less than 2 minutes. It can
be done, but you are going to have an extremely difficult time handling all
of the error messages that will pop up due to latency and congestion.
2. You can use a network share if you choose to. The only impact is that
there will be a slightly longer delay as your backups transit across your
network card instead of to the local disk. The negative impact is that your
backups are streaming down your network card which impacts network
throughput. But, that impact is similar to what happens if you back up to
local disk and then copy the backup over, so that consideration is
essentially a wash.
3. Watch you full backups carefully. They will block the transaction log
backups which can cause all of your alarms to go off.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||A one minute transaction log backup is VERY ambitious. Most people go for between 5 and 15 minutes. If you test lab this with production-like equipment you will understand why 1-min intervals is so difficult to achieve on SQL2K.
If the network connection is broken, the transaction log copy job will retry the copy the next time it is scheduled to run. No data will be lost. It will keep retrying until the logs are successfully copied or the out-of-synch time is reached.
With an interval of 1-min performance could be a real concern.
i am planning to implement logshipping in sql 2000 which
is already a pulisher for transactional replication.
i am planning to take transaction log backup in the
interval of 1(one) minute.
if network connection broken will it affect restoring at
desination server?
can i make the share for transaction log backup folder on
network instead of production server?
overall will it have any negative impacton source server.
Pls advice
Thanks
Biju
1. Don't try to do log shipping at an interval less than 2 minutes. It can
be done, but you are going to have an extremely difficult time handling all
of the error messages that will pop up due to latency and congestion.
2. You can use a network share if you choose to. The only impact is that
there will be a slightly longer delay as your backups transit across your
network card instead of to the local disk. The negative impact is that your
backups are streaming down your network card which impacts network
throughput. But, that impact is similar to what happens if you back up to
local disk and then copy the backup over, so that consideration is
essentially a wash.
3. Watch you full backups carefully. They will block the transaction log
backups which can cause all of your alarms to go off.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||A one minute transaction log backup is VERY ambitious. Most people go for between 5 and 15 minutes. If you test lab this with production-like equipment you will understand why 1-min intervals is so difficult to achieve on SQL2K.
If the network connection is broken, the transaction log copy job will retry the copy the next time it is scheduled to run. No data will be lost. It will keep retrying until the logs are successfully copied or the out-of-synch time is reached.
With an interval of 1-min performance could be a real concern.
Wednesday, March 21, 2012
LogScan in progress
Hello,
We have a mixed replication environment with SQL Server transactional
replication and Datamirror replication (with DB2). Yesterday we upgraded to
SQL Server 2005 and the transactional replication does not work.
The log reader message is "Logscan in progress. Approximately 4254920 log
records scanned in pass # 1, elapsed time 7620 (ms).". The Subscription
Watcher tells that all subscriptions are uninitialized. But actually, I have
not subscription to initialize (there are Datamirror). And, in any case, I
cannot reinitialize the subscription because the initial synchronization was
made manually.
Now, all pending changes are in the transaction log of the publisher database.
What can I do? Is to drop and recreate the publication the only way to solve
this issue?
Thank you in advanced,
qwalgrande
You need to contact DataMirror to learn how to make their product work with
SQL Server 2005.
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
"qwalgrande" <qwalgrande*nospam*@.yahoo.es> wrote in message
news:19C4184F-C544-43A3-B6AD-74E170047129@.microsoft.com...
> Hello,
> We have a mixed replication environment with SQL Server transactional
> replication and Datamirror replication (with DB2). Yesterday we upgraded
> to
> SQL Server 2005 and the transactional replication does not work.
> The log reader message is "Logscan in progress. Approximately 4254920 log
> records scanned in pass # 1, elapsed time 7620 (ms).". The Subscription
> Watcher tells that all subscriptions are uninitialized. But actually, I
> have
> not subscription to initialize (there are Datamirror). And, in any case, I
> cannot reinitialize the subscription because the initial synchronization
> was
> made manually.
> Now, all pending changes are in the transaction log of the publisher
> database.
> What can I do? Is to drop and recreate the publication the only way to
> solve
> this issue?
> Thank you in advanced,
> --
> qwalgrande
We have a mixed replication environment with SQL Server transactional
replication and Datamirror replication (with DB2). Yesterday we upgraded to
SQL Server 2005 and the transactional replication does not work.
The log reader message is "Logscan in progress. Approximately 4254920 log
records scanned in pass # 1, elapsed time 7620 (ms).". The Subscription
Watcher tells that all subscriptions are uninitialized. But actually, I have
not subscription to initialize (there are Datamirror). And, in any case, I
cannot reinitialize the subscription because the initial synchronization was
made manually.
Now, all pending changes are in the transaction log of the publisher database.
What can I do? Is to drop and recreate the publication the only way to solve
this issue?
Thank you in advanced,
qwalgrande
You need to contact DataMirror to learn how to make their product work with
SQL Server 2005.
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
"qwalgrande" <qwalgrande*nospam*@.yahoo.es> wrote in message
news:19C4184F-C544-43A3-B6AD-74E170047129@.microsoft.com...
> Hello,
> We have a mixed replication environment with SQL Server transactional
> replication and Datamirror replication (with DB2). Yesterday we upgraded
> to
> SQL Server 2005 and the transactional replication does not work.
> The log reader message is "Logscan in progress. Approximately 4254920 log
> records scanned in pass # 1, elapsed time 7620 (ms).". The Subscription
> Watcher tells that all subscriptions are uninitialized. But actually, I
> have
> not subscription to initialize (there are Datamirror). And, in any case, I
> cannot reinitialize the subscription because the initial synchronization
> was
> made manually.
> Now, all pending changes are in the transaction log of the publisher
> database.
> What can I do? Is to drop and recreate the publication the only way to
> solve
> this issue?
> Thank you in advanced,
> --
> qwalgrande
LOGREADER NOT START - No body can help?
When I try to start the agent (replication monitor->Agents -> log reader
Agent - with red cross). show me this error :
22022 sqlserveragent error: request to run job svr-personal-origen-1 (from
user personal\alioscha) refused because the job has been suspended.
SO windows 2000. server 2000 sp1
ANY HELP WILL BE APPRECIATED.
right click on this job and start it under sa.
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
"Alioscha Debali" <adebali@.copetel.com.ar> wrote in message
news:%23RpNHcHNFHA.568@.TK2MSFTNGP09.phx.gbl...
> When I try to start the agent (replication monitor->Agents -> log reader
> Agent - with red cross). show me this error :
> 22022 sqlserveragent error: request to run job svr-personal-origen-1 (from
> user personal\alioscha) refused because the job has been suspended.
> SO windows 2000. server 2000 sp1
>
> ANY HELP WILL BE APPRECIATED.
>
>
>
|||Hilary thank you for your answer, But I have tried and it did not work.
"Hilary Cotter" wrote:
> right click on this job and start it under sa.
> --
> 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
> "Alioscha Debali" <adebali@.copetel.com.ar> wrote in message
> news:%23RpNHcHNFHA.568@.TK2MSFTNGP09.phx.gbl...
>
>
|||Hilary. Into folder Admin->Jobs , There is a Job "SVR-PERSONAL-ORIGEN-1"
with red cross ( category REPL-LogReader) YES/ NO (job susp)/YES/SUSP
Right click.->General Label. Owner: sa.
Do I doing something wrong?
Thank again for your help.
"Alioscha Debali" <Alioscha Debali@.discussions.microsoft.com> escribi en el
mensaje news:84FDD7B9-91A9-4635-9174-BA75C3C4AE1A@.microsoft.com...[vbcol=seagreen]
> Hilary thank you for your answer, But I have tried and it did not work.
>
>
> "Hilary Cotter" wrote:
reader[vbcol=seagreen]
(from[vbcol=seagreen]
Agent - with red cross). show me this error :
22022 sqlserveragent error: request to run job svr-personal-origen-1 (from
user personal\alioscha) refused because the job has been suspended.
SO windows 2000. server 2000 sp1
ANY HELP WILL BE APPRECIATED.
right click on this job and start it under sa.
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
"Alioscha Debali" <adebali@.copetel.com.ar> wrote in message
news:%23RpNHcHNFHA.568@.TK2MSFTNGP09.phx.gbl...
> When I try to start the agent (replication monitor->Agents -> log reader
> Agent - with red cross). show me this error :
> 22022 sqlserveragent error: request to run job svr-personal-origen-1 (from
> user personal\alioscha) refused because the job has been suspended.
> SO windows 2000. server 2000 sp1
>
> ANY HELP WILL BE APPRECIATED.
>
>
>
|||Hilary thank you for your answer, But I have tried and it did not work.
"Hilary Cotter" wrote:
> right click on this job and start it under sa.
> --
> 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
> "Alioscha Debali" <adebali@.copetel.com.ar> wrote in message
> news:%23RpNHcHNFHA.568@.TK2MSFTNGP09.phx.gbl...
>
>
|||Hilary. Into folder Admin->Jobs , There is a Job "SVR-PERSONAL-ORIGEN-1"
with red cross ( category REPL-LogReader) YES/ NO (job susp)/YES/SUSP
Right click.->General Label. Owner: sa.
Do I doing something wrong?
Thank again for your help.
"Alioscha Debali" <Alioscha Debali@.discussions.microsoft.com> escribi en el
mensaje news:84FDD7B9-91A9-4635-9174-BA75C3C4AE1A@.microsoft.com...[vbcol=seagreen]
> Hilary thank you for your answer, But I have tried and it did not work.
>
>
> "Hilary Cotter" wrote:
reader[vbcol=seagreen]
(from[vbcol=seagreen]
Logreader access violation
Hi everyone,
I am setting up Transaction Replication on a MSSQL 2000 8.0.194. Everything
was going fine until the log reader stopped with a "An access violation
occurred" error.
I tried setting up a publication on another test database on the same server
to make sure the problem was not with the database it self and encountered
the same error.
In the ReplExceptLogRdr.log I am getting the following error:
Microsoft SQL Server Replication: Exception Stack Dump
************************************************** *****
Computer type is AT/AT COMPATIBLE.
Bios Version is DELL - 1
Phoenix ROM BIOS PLUS Version 1.10 A10Current local time is Fri Apr 13
15:16:41 2007
4 Intel x86 level 15, 2392 Mhz processor(s).
Windows NT 5.2 Build 3790 CSD .
MemoryLoad 62%TotalPhys 2047 MB
AvailPhys 1481 MBTotalPageFile 4095 MB
************************************************** *****
An exception was caught
in LOGREAD.EXE
* Exception Address = 00000001
* Exception Code = c0000005
*
************************************************** *****
Module NameReturn AddressLocation
[No Module Info]003678f000000001
[No Module Info]0040abd5003678f0
logread0040dec90040abd5
logread0040aa5c0040dec9
logread77e4f38c0040aa5c
kernel3200000000TerminateThread + 113
I have tested setting up replication using the same database on the users
reporting server and everything went fine. I have tried giving the folder
that contains the Distributor database and logfile access to "Everyone".
The Event Viewer show the following error and information:
[SQLSERVERAgent Error]
Microsoft SQL Server Replication : The LOGREAD.EXE executable is terminating
abnormally because it hit an exception. Exception Code c0000005. Check file
ReplExceptLogRdr.log for details.
[Information]
SubSystem Message - Job 'CL-SQL-CLUAT-1'
(0x7A865965F727AB4CA60CC19D5A5EEEA8), step 2 - An access violation occurred.
I tried changing the Logreaders agents verbose level to 3, but nothing extra
appeared in the sqlserver log.
Before I set up replication I had to change the logon the sqlserver agent
was running from the system account to a windows user with Admin rights. The
user also has sql server admin rights.
I am kind of stuck now as I don't know what else I can do to further
investigate the problem.
Any help would really be appreciated.
Thanks,
SQLNewbie
Hi Hillary,
Thanks for your time on this. I did post the contents of the
ReplExceptLogRdr.log in me initial post. It was located in the C:\Program
Files\Microsoft SQL Server\MSSQL\LOG folder. Is this the same log you are
referring to? I am not sure what you mean by (IIRC).
I wasn't sure if this was a bug so I haven't applied any patches.
Is this a user rights problem? That is the user running the SQL Server agent
has insufficient rights, because the user I created has Admin rights for
Windows and System Admin rights for SQL Server.
Thanks,
SQLNEwbie
"Hilary Cotter" wrote:
> I get these from time to time. Did you check ReplExceptLogRdr.log IIRC it
> will be found in windows\system32
> Also does this apply?
> http://support.microsoft.com/kb/872843/EN-US/
> --
> 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
>
> "sqlnewbie" <sqlnewbie@.discussions.microsoft.com> wrote in message
> news:C5CCC218-2858-42BD-97BE-6C0B3AB1054E@.microsoft.com...
>
>
|||Hi,
Just a quick update on this problem. I applied SP4 and that has resolved the
problem.
Thanks
"sqlnewbie" wrote:
[vbcol=seagreen]
> Hi Hillary,
> Thanks for your time on this. I did post the contents of the
> ReplExceptLogRdr.log in me initial post. It was located in the C:\Program
> Files\Microsoft SQL Server\MSSQL\LOG folder. Is this the same log you are
> referring to? I am not sure what you mean by (IIRC).
> I wasn't sure if this was a bug so I haven't applied any patches.
> Is this a user rights problem? That is the user running the SQL Server agent
> has insufficient rights, because the user I created has Admin rights for
> Windows and System Admin rights for SQL Server.
> Thanks,
> SQLNEwbie
> "Hilary Cotter" wrote:
I am setting up Transaction Replication on a MSSQL 2000 8.0.194. Everything
was going fine until the log reader stopped with a "An access violation
occurred" error.
I tried setting up a publication on another test database on the same server
to make sure the problem was not with the database it self and encountered
the same error.
In the ReplExceptLogRdr.log I am getting the following error:
Microsoft SQL Server Replication: Exception Stack Dump
************************************************** *****
Computer type is AT/AT COMPATIBLE.
Bios Version is DELL - 1
Phoenix ROM BIOS PLUS Version 1.10 A10Current local time is Fri Apr 13
15:16:41 2007
4 Intel x86 level 15, 2392 Mhz processor(s).
Windows NT 5.2 Build 3790 CSD .
MemoryLoad 62%TotalPhys 2047 MB
AvailPhys 1481 MBTotalPageFile 4095 MB
************************************************** *****
An exception was caught
in LOGREAD.EXE
* Exception Address = 00000001
* Exception Code = c0000005
*
************************************************** *****
Module NameReturn AddressLocation
[No Module Info]003678f000000001
[No Module Info]0040abd5003678f0
logread0040dec90040abd5
logread0040aa5c0040dec9
logread77e4f38c0040aa5c
kernel3200000000TerminateThread + 113
I have tested setting up replication using the same database on the users
reporting server and everything went fine. I have tried giving the folder
that contains the Distributor database and logfile access to "Everyone".
The Event Viewer show the following error and information:
[SQLSERVERAgent Error]
Microsoft SQL Server Replication : The LOGREAD.EXE executable is terminating
abnormally because it hit an exception. Exception Code c0000005. Check file
ReplExceptLogRdr.log for details.
[Information]
SubSystem Message - Job 'CL-SQL-CLUAT-1'
(0x7A865965F727AB4CA60CC19D5A5EEEA8), step 2 - An access violation occurred.
I tried changing the Logreaders agents verbose level to 3, but nothing extra
appeared in the sqlserver log.
Before I set up replication I had to change the logon the sqlserver agent
was running from the system account to a windows user with Admin rights. The
user also has sql server admin rights.
I am kind of stuck now as I don't know what else I can do to further
investigate the problem.
Any help would really be appreciated.
Thanks,
SQLNewbie
Hi Hillary,
Thanks for your time on this. I did post the contents of the
ReplExceptLogRdr.log in me initial post. It was located in the C:\Program
Files\Microsoft SQL Server\MSSQL\LOG folder. Is this the same log you are
referring to? I am not sure what you mean by (IIRC).
I wasn't sure if this was a bug so I haven't applied any patches.
Is this a user rights problem? That is the user running the SQL Server agent
has insufficient rights, because the user I created has Admin rights for
Windows and System Admin rights for SQL Server.
Thanks,
SQLNEwbie
"Hilary Cotter" wrote:
> I get these from time to time. Did you check ReplExceptLogRdr.log IIRC it
> will be found in windows\system32
> Also does this apply?
> http://support.microsoft.com/kb/872843/EN-US/
> --
> 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
>
> "sqlnewbie" <sqlnewbie@.discussions.microsoft.com> wrote in message
> news:C5CCC218-2858-42BD-97BE-6C0B3AB1054E@.microsoft.com...
>
>
|||Hi,
Just a quick update on this problem. I applied SP4 and that has resolved the
problem.
Thanks
"sqlnewbie" wrote:
[vbcol=seagreen]
> Hi Hillary,
> Thanks for your time on this. I did post the contents of the
> ReplExceptLogRdr.log in me initial post. It was located in the C:\Program
> Files\Microsoft SQL Server\MSSQL\LOG folder. Is this the same log you are
> referring to? I am not sure what you mean by (IIRC).
> I wasn't sure if this was a bug so I haven't applied any patches.
> Is this a user rights problem? That is the user running the SQL Server agent
> has insufficient rights, because the user I created has Admin rights for
> Windows and System Admin rights for SQL Server.
> Thanks,
> SQLNEwbie
> "Hilary Cotter" wrote:
Monday, February 20, 2012
Login Problem
I just tried to create a Transactional Replication and it failed because the
Login for sa failed...
I assume that the destination server (for Push Subscription) doesn't
recognize the sa of the Distributor
What can be done to solve that (when running the wizard I wasn't given any
chance to solve that)
Thank you,
Samuel
if this is a pull subscription you must make sure that the sa account, the
SQL Server agent account on the subscriber, or the account that you are
using to pull the subscription has dbo rights on the distribution database,
and is in the PAL of the publication database.
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
"Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
news:eeCvEFN5GHA.4868@.TK2MSFTNGP03.phx.gbl...
> I just tried to create a Transactional Replication and it failed because
> the Login for sa failed...
> I assume that the destination server (for Push Subscription) doesn't
> recognize the sa of the Distributor
> What can be done to solve that (when running the wizard I wasn't given any
> chance to solve that)
> Thank you,
> Samuel
>
|||It is a push subscription
Samuel
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OG4si8N5GHA.4256@.TK2MSFTNGP03.phx.gbl...
> if this is a pull subscription you must make sure that the sa account, the
> SQL Server agent account on the subscriber, or the account that you are
> using to pull the subscription has dbo rights on the distribution
> database, and is in the PAL of the publication database.
> --
> 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
> "Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
> news:eeCvEFN5GHA.4868@.TK2MSFTNGP03.phx.gbl...
>
|||Samuel,
please see if this applies to your issue:
http://support.microsoft.com/default...b;en-us;320773
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Your publisherlogin property must be the sa account (or an account in the
dbo role in the distribution database and the dbo role in the publication
database). can you ensure that this is the case?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
news:O$JJeDO5GHA.2596@.TK2MSFTNGP06.phx.gbl...
> It is a push subscription
> Samuel
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OG4si8N5GHA.4256@.TK2MSFTNGP03.phx.gbl...
>
Login for sa failed...
I assume that the destination server (for Push Subscription) doesn't
recognize the sa of the Distributor
What can be done to solve that (when running the wizard I wasn't given any
chance to solve that)
Thank you,
Samuel
if this is a pull subscription you must make sure that the sa account, the
SQL Server agent account on the subscriber, or the account that you are
using to pull the subscription has dbo rights on the distribution database,
and is in the PAL of the publication database.
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
"Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
news:eeCvEFN5GHA.4868@.TK2MSFTNGP03.phx.gbl...
> I just tried to create a Transactional Replication and it failed because
> the Login for sa failed...
> I assume that the destination server (for Push Subscription) doesn't
> recognize the sa of the Distributor
> What can be done to solve that (when running the wizard I wasn't given any
> chance to solve that)
> Thank you,
> Samuel
>
|||It is a push subscription
Samuel
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OG4si8N5GHA.4256@.TK2MSFTNGP03.phx.gbl...
> if this is a pull subscription you must make sure that the sa account, the
> SQL Server agent account on the subscriber, or the account that you are
> using to pull the subscription has dbo rights on the distribution
> database, and is in the PAL of the publication database.
> --
> 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
> "Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
> news:eeCvEFN5GHA.4868@.TK2MSFTNGP03.phx.gbl...
>
|||Samuel,
please see if this applies to your issue:
http://support.microsoft.com/default...b;en-us;320773
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Your publisherlogin property must be the sa account (or an account in the
dbo role in the distribution database and the dbo role in the publication
database). can you ensure that this is the case?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
news:O$JJeDO5GHA.2596@.TK2MSFTNGP06.phx.gbl...
> It is a push subscription
> Samuel
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OG4si8N5GHA.4256@.TK2MSFTNGP03.phx.gbl...
>
Subscribe to:
Posts (Atom)