Sunday, February 26, 2012
Enable/Disable Triggers?
Is it possible to enable/disable triggers without dropping them'
I want to disbale them sometimes to prevent firing them
thanksLook in the BOL, for the syntax of ALTER TABLE:
ALTER TABLE
(...)
| { ENABLE | DISABLE } TRIGGER
{ ALL | trigger_name [ ,...n ] }
Should do the trick,
HTH, Jens Suessmeyer.|||Yes, I use undocumented stored procedure to do that
-- to diable all
EXEC sp_MSForEachTable N'ALTER TABLE ? DISABLE TRIGGER ALL'
GO
-- to enable all
EXEC sp_MSForEachTable N'ALTER TABLE ? ENABLE TRIGGER ALL'
GO
"perspolis" <rezarms@.hotmail.com> wrote in message
news:%23FzbAHY%23FHA.740@.TK2MSFTNGP12.phx.gbl...
> Hi all
> Is it possible to enable/disable triggers without dropping them'
> I want to disbale them sometimes to prevent firing them
>
> thanks
>|||thanks so much..
Is there any option in SqlServer Enterprise manager to do that visually?/
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1133776901.386512.272690@.f14g2000cwb.googlegroups.com...
> Look in the BOL, for the syntax of ALTER TABLE:
> ALTER TABLE
> (...)
> | { ENABLE | DISABLE } TRIGGER
> { ALL | trigger_name [ ,...n ] }
> Should do the trick,
> HTH, Jens Suessmeyer.
>|||Although the Procedure still works in SQLServer 2005, you have to keep
in mind that this could be obsolete in further versions.
HTH, Jens Suessmeyer.|||Well, no.|||Be aware of the fact that once disabled, triggers stay disabled for every
connection until re-enabled again. In other words - if the purpose of the
trigger is to enforce a business rule, that rule will not be enforced by the
server during the time the trigger is disabled.
ML
http://milambda.blogspot.com/|||Hopefully by then he will find a solution that doesn't involve disabling
triggers.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1133777368.327941.177950@.o13g2000cwo.googlegroups.com...
> Although the Procedure still works in SQLServer 2005, you have to keep
> in mind that this could be obsolete in further versions.
> HTH, Jens Suessmeyer.
>
Enable/Disable Trigger
What would be a workaround to using the alter table with disable and enable
triggers listed below.
Thanks,
CREATE PROCEDURE dbo.K_ManualMoves
as
BEGIN
alter table T_Moves
disable trigger iu_t_Moves
alter table T_Fees_Moves
disable trigger iu_t_Fees
Begin
Body Stored Procedure
End
alter table T_Moves
enable trigger iu_t_Moves
alter table T_Fees_Moves
enable trigger iu_t_Fees
End
GOWhy do you need a workaround, if you want to disable the trigger use Alter
table as you have done, Or is there some reason you do not want to disable
the triggers? Without seeing what the rest of the code is it is difficult to
understand your problem
Mike John
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:09A5FD91-8F76-4431-B17B-0F4D4FF85B24@.microsoft.com...
> I have a stored procedure disable and enable triggers on several tables.
> What would be a workaround to using the alter table with disable and
> enable
> triggers listed below.
> Thanks,
> CREATE PROCEDURE dbo.K_ManualMoves
> as
> BEGIN
> alter table T_Moves
> disable trigger iu_t_Moves
> alter table T_Fees_Moves
> disable trigger iu_t_Fees
> Begin
> Body Stored Procedure
> End
> alter table T_Moves
> enable trigger iu_t_Moves
> alter table T_Fees_Moves
> enable trigger iu_t_Fees
> End
> GO|||That's how to do it.
I'm guessing your concern is that the triggers would be disabled while a
process that should fire them runs. In that case, the most solid option
is to have the triggers manage themselves, based on data being modified
(like a source column indicating what process changed the data), or
environment settings (like user or application) or something else
limited to the scope of the modification.
Joe K. wrote:
> I have a stored procedure disable and enable triggers on several tables.
> What would be a workaround to using the alter table with disable and enabl
e
> triggers listed below.
> Thanks,
> CREATE PROCEDURE dbo.K_ManualMoves
> as
> BEGIN
> alter table T_Moves
> disable trigger iu_t_Moves
> alter table T_Fees_Moves
> disable trigger iu_t_Fees
> Begin
> Body Stored Procedure
> End
> alter table T_Moves
> enable trigger iu_t_Moves
> alter table T_Fees_Moves
> enable trigger iu_t_Fees
> End
> GO|||Joe K. (Joe K.@.discussions.microsoft.com) writes:
> I have a stored procedure disable and enable triggers on several tables.
> What would be a workaround to using the alter table with disable and
> enable triggers listed below.
In the stored procedure create a temp table:
CREATE TABLE #trigger$disabled(a int NOT NULL)
In the trigger you would add
IF object_id('tempdb..#trigger$disabled') IS NOT NULL
RETURN
Even better you can disable only the part that you that you will violate.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
Enable/Disable SQL Server login
Is there a way that I can enable/disable logins using SQL Authentication? Or similar function like Oracle's ALTER user LOCK/UNLOCK.
Thanks & Regards.
DennisYes, you can disable/enable logins using:
ALTER LOGIN login_name DISABLE
ALTER LOGIN login_name ENABLE
This works with any login, not only SQL logins.
Thanks
Laurentiu
ENABLE/DISABLE primarykeys,foreignkeys & indexes
I need to ENABLE & Disable the primarykeys,foreignkeys & indexes of a table
I have tried
ALTER TABLE employees DISABLE PRIMARY KEY
but it shows the following error
Incorrect syntax near the keyword 'PRIMARY'.
can u help me?
Thanks,
Soura
As a primary key is supported by a unique index, you cannot disable it. A
unique index has to always enforce uniqueness.
Please check the proper syntax in the Books Online. DISABLE is only used for
triggers.
To disable a constraint, you must use the NOCHECK option. And the BOL
states:
{ CHECK | NOCHECK} CONSTRAINT
Specifies that constraint_name is enabled or disabled. When disabled, future
inserts or updates to the column are not validated against the constraint
conditions. This option can only be used with FOREIGN KEY and CHECK
constraints.
To no longer enforce the primary key's properties, you have to DROP the
constraint, which will drop the unique index.
Please see BOL for complete syntax details.
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:3CA0935E-35E9-46D4-8D2F-DD317FECFAB1@.microsoft.com...
> hi,
> I need to ENABLE & Disable the primarykeys,foreignkeys & indexes of a
> table
> I have tried
> ALTER TABLE employees DISABLE PRIMARY KEY
> but it shows the following error
> Incorrect syntax near the keyword 'PRIMARY'.
> can u help me?
> Thanks,
> Soura
>
ENABLE/DISABLE primarykeys,foreignkeys & indexes
I need to ENABLE & Disable the primarykeys,foreignkeys & indexes of a table
I have tried
ALTER TABLE employees DISABLE PRIMARY KEY
but it shows the following error
Incorrect syntax near the keyword 'PRIMARY'.
can u help me?
Thanks,
SouraAs a primary key is supported by a unique index, you cannot disable it. A
unique index has to always enforce uniqueness.
Please check the proper syntax in the Books Online. DISABLE is only used for
triggers.
To disable a constraint, you must use the NOCHECK option. And the BOL
states:
{ CHECK | NOCHECK} CONSTRAINT
Specifies that constraint_name is enabled or disabled. When disabled, future
inserts or updates to the column are not validated against the constraint
conditions. This option can only be used with FOREIGN KEY and CHECK
constraints.
To no longer enforce the primary key's properties, you have to DROP the
constraint, which will drop the unique index.
Please see BOL for complete syntax details.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:3CA0935E-35E9-46D4-8D2F-DD317FECFAB1@.microsoft.com...
> hi,
> I need to ENABLE & Disable the primarykeys,foreignkeys & indexes of a
> table
> I have tried
> ALTER TABLE employees DISABLE PRIMARY KEY
> but it shows the following error
> Incorrect syntax near the keyword 'PRIMARY'.
> can u help me?
> Thanks,
> Soura
>|||hi,
I need to DISABLE/ENABLE all the foreign keys in a DataBase
Is it possible through Query?
Can u help me?
Thanks
Soura
"Kalen Delaney" wrote:
> As a primary key is supported by a unique index, you cannot disable it. A
> unique index has to always enforce uniqueness.
> Please check the proper syntax in the Books Online. DISABLE is only used for
> triggers.
> To disable a constraint, you must use the NOCHECK option. And the BOL
> states:
> { CHECK | NOCHECK} CONSTRAINT
> Specifies that constraint_name is enabled or disabled. When disabled, future
> inserts or updates to the column are not validated against the constraint
> conditions. This option can only be used with FOREIGN KEY and CHECK
> constraints.
> To no longer enforce the primary key's properties, you have to DROP the
> constraint, which will drop the unique index.
> Please see BOL for complete syntax details.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "SouRa" <SouRa@.discussions.microsoft.com> wrote in message
> news:3CA0935E-35E9-46D4-8D2F-DD317FECFAB1@.microsoft.com...
> > hi,
> >
> > I need to ENABLE & Disable the primarykeys,foreignkeys & indexes of a
> > table
> >
> > I have tried
> > ALTER TABLE employees DISABLE PRIMARY KEY
> >
> > but it shows the following error
> > Incorrect syntax near the keyword 'PRIMARY'.
> >
> > can u help me?
> >
> > Thanks,
> > Soura
> >
>
>
ENABLE/DISABLE primarykeys,foreignkeys & indexes
I need to ENABLE & Disable the primarykeys,foreignkeys & indexes of a table
I have tried
ALTER TABLE employees DISABLE PRIMARY KEY
but it shows the following error
Incorrect syntax near the keyword 'PRIMARY'.
can u help me?
Thanks,
SouraAs a primary key is supported by a unique index, you cannot disable it. A
unique index has to always enforce uniqueness.
Please check the proper syntax in the Books Online. DISABLE is only used for
triggers.
To disable a constraint, you must use the NOCHECK option. And the BOL
states:
{ CHECK | NOCHECK} CONSTRAINT
Specifies that constraint_name is enabled or disabled. When disabled, future
inserts or updates to the column are not validated against the constraint
conditions. This option can only be used with FOREIGN KEY and CHECK
constraints.
To no longer enforce the primary key's properties, you have to DROP the
constraint, which will drop the unique index.
Please see BOL for complete syntax details.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:3CA0935E-35E9-46D4-8D2F-DD317FECFAB1@.microsoft.com...
> hi,
> I need to ENABLE & Disable the primarykeys,foreignkeys & indexes of a
> table
> I have tried
> ALTER TABLE employees DISABLE PRIMARY KEY
> but it shows the following error
> Incorrect syntax near the keyword 'PRIMARY'.
> can u help me?
> Thanks,
> Soura
>
Enable/Disable primary keys,FK,indexes
I need to ENABLE & Disable the primarykeys,foreignkeys & indexes of a table
through query
I have tried
ALTER TABLE employees DISABLE PRIMARY KEY
but it shows the following error
Incorrect syntax near the keyword 'PRIMARY'.
can u help me?
Thanks,
SouraAnswered in first post of the exact same question...
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:7DFCB99D-2BD3-4964-A279-83E0A2683159@.microsoft.com...
> hi,
> I need to ENABLE & Disable the primarykeys,foreignkeys & indexes of a
> table
> through query
> I have tried
> ALTER TABLE employees DISABLE PRIMARY KEY
> but it shows the following error
> Incorrect syntax near the keyword 'PRIMARY'.
> can u help me?
> Thanks,
> Soura
>
Enable/Disable primary keys,FK,indexes
I need to ENABLE & Disable the primarykeys,foreignkeys & indexes of a table
through query
I have tried
ALTER TABLE employees DISABLE PRIMARY KEY
but it shows the following error
Incorrect syntax near the keyword 'PRIMARY'.
can u help me?
Thanks,
SouraAnswered in first post of the exact same question...
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:7DFCB99D-2BD3-4964-A279-83E0A2683159@.microsoft.com...
> hi,
> I need to ENABLE & Disable the primarykeys,foreignkeys & indexes of a
> table
> through query
> I have tried
> ALTER TABLE employees DISABLE PRIMARY KEY
> but it shows the following error
> Incorrect syntax near the keyword 'PRIMARY'.
> can u help me?
> Thanks,
> Soura
>
Enable/Disable primary keys,FK,indexes
I need to ENABLE & Disable the primarykeys,foreignkeys & indexes of a table
through query
I have tried
ALTER TABLE employees DISABLE PRIMARY KEY
but it shows the following error
Incorrect syntax near the keyword 'PRIMARY'.
can u help me?
Thanks,
Soura
Answered in first post of the exact same question...
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:7DFCB99D-2BD3-4964-A279-83E0A2683159@.microsoft.com...
> hi,
> I need to ENABLE & Disable the primarykeys,foreignkeys & indexes of a
> table
> through query
> I have tried
> ALTER TABLE employees DISABLE PRIMARY KEY
> but it shows the following error
> Incorrect syntax near the keyword 'PRIMARY'.
> can u help me?
> Thanks,
> Soura
>
Friday, February 24, 2012
Enable/Disable of Toogle
a item. and the toogled ability is enabled.
.
Can I set if the group an can be toogled according some custom code?Hi
Unless you are using dynamic SQL then you will need to return the same
columns back from your query and use the client to display/hide the column
e.g.
SELECT CASE @.isvisible THEN col1 ELSE '' END AS col1,
col2,
CASE @.isvisible THEN col3 ELSE '' END AS col3
FROM MyTable
John
"ad" <flying@.wfes.tcc.edu.tw> wrote in message
news:OwKw5DAzFHA.3408@.TK2MSFTNGP09.phx.gbl...
>I we a matrix in my report, I can set the 'Visibility can be toggled by'
>to a item. and the toogled ability is enabled.
> .
> Can I set if the group an can be toogled according some custom code?
>
Enable/Disable of Toogle
a item. and the toogled ability is enabled.
.
Can I set if the group an can be toogled according some custom code?Hi
Unless you are using dynamic SQL then you will need to return the same
columns back from your query and use the client to display/hide the column
e.g.
SELECT CASE @.isvisible THEN col1 ELSE '' END AS col1,
col2,
CASE @.isvisible THEN col3 ELSE '' END AS col3
FROM MyTable
John
"ad" <flying@.wfes.tcc.edu.tw> wrote in message
news:OwKw5DAzFHA.3408@.TK2MSFTNGP09.phx.gbl...
>I we a matrix in my report, I can set the 'Visibility can be toggled by'
>to a item. and the toogled ability is enabled.
> .
> Can I set if the group an can be toogled according some custom code?
>
Enable/Disable of Toogle
a item. and the toogled ability is enabled.
..
Can I set if the group an can be toogled according some custom code?
Hi
Unless you are using dynamic SQL then you will need to return the same
columns back from your query and use the client to display/hide the column
e.g.
SELECT CASE @.isvisible THEN col1 ELSE '' END AS col1,
col2,
CASE @.isvisible THEN col3 ELSE '' END AS col3
FROM MyTable
John
"ad" <flying@.wfes.tcc.edu.tw> wrote in message
news:OwKw5DAzFHA.3408@.TK2MSFTNGP09.phx.gbl...
>I we a matrix in my report, I can set the 'Visibility can be toggled by'
>to a item. and the toogled ability is enabled.
> .
> Can I set if the group an can be toogled according some custom code?
>
Enable/disable logging dynamically
The use case is one where multiple loggers are defined in a package (custom and stock) and I'd like to toggle the execution tracing on a per logger basis.
I realize "logger toggling" can be done programmatically, but I'm wondering if that's the only way to accomplish the objective.
The behaviour of the logging cannot be modified at runtime. Also, logging different events in different log providers for same executable is not possible as well. It's a great idea for a future version tough.
What you can do is decide who can log, what log providers should each executable use, and what events for each executable you want to log at design time. (e.g.: I can log "ExecuteSQLExecutingQuery" from the ExecuteSQL task in SQL server, and WMIDataReaderOperation" from the WMI Data Reader task in a file).
Thanks,
Ovidiu
|||You may also consider investigating creating a custom logging solution using Event Handlers. You have a great deal of control over how they operate and you can even use variables and configurations to control them.
Jamie Thomson had a blog about this sometime back... here is the link: http://blogs.conchango.com/jamiethomson/archive/2005/06/11/1593.aspx
Enable/disable logging dynamically
The use case is one where multiple loggers are defined in a package (custom and stock) and I'd like to toggle the execution tracing on a per logger basis.
I realize "logger toggling" can be done programmatically, but I'm wondering if that's the only way to accomplish the objective.
The behaviour of the logging cannot be modified at runtime. Also, logging different events in different log providers for same executable is not possible as well. It's a great idea for a future version tough.
What you can do is decide who can log, what log providers should each executable use, and what events for each executable you want to log at design time. (e.g.: I can log "ExecuteSQLExecutingQuery" from the ExecuteSQL task in SQL server, and WMIDataReaderOperation" from the WMI Data Reader task in a file).
Thanks,
Ovidiu
|||You may also consider investigating creating a custom logging solution using Event Handlers. You have a great deal of control over how they operate and you can even use variables and configurations to control them.
Jamie Thomson had a blog about this sometime back... here is the link: http://blogs.conchango.com/jamiethomson/archive/2005/06/11/1593.aspx
Enable/Disable Job with SMO
I am trying to enable/disable a job using a using smo in a script task with the following code
Imports System.Object
Imports Microsoft.SqlServer.Management.Common
Imports Microsoft.SqlServer.Management.Smo
Imports Microsoft.SqlServer.Management.Smo.Agent
Imports Microsoft.SqlServer.Management.Smo.SqlSmoObject
Imports Microsoft.SqlServer.Management.Smo.SmoObjectBase
Imports Microsoft.SqlServer.Management.Smo.NamedSmoObject
Imports Microsoft.SqlServer.Management.Smo.Agent.Job
Imports Microsoft.SqlServer.Management.Smo.Agent.Jobserver
Imports Microsoft.SqlServer.Management.Smo.Agent.AgentObjectBase
Public Class ScriptMain
Public Sub Main()
Dim strJobserver As JobServer
Dim strJob As Job
Dim srv As Server
srv = New Server("conchango-vpc")
strJob = New Job(srv.JobServer, "test")
strJob.IsEnabled = True
strJob.Alter()
Dts.TaskResult = Dts.Results.Success
End Sub
End Class
and i get an error at the alter point.
when code is changed to using the following line
srv.Jobserver.Alter()
it runs successfully but no change is made to the job.
What am I missing?
Ifaka Enefe
Conchango
Instead of: Use:
strJob = New Job(srv.JobServer, "test")
strJob = srv.JobServer.Jobs("test")
I've got the followinng inside a class library:
Server serv; Job jb; serv = new Server(this.strServerName); jb = serv.JobServer.Jobs(this.strJobName); if (strJobEnabledStatus=="True") { jb.IsEnabled = true; } else { jb.IsEnabled=false; } jb.Alter();
And it complains about
serv.JobServer.Jobs(this.strJobName)
Any ideas? I aint much a developer I'm afraid so I'm at a bit of a loss here.
Thanks
Jamie|||s'all right. I've found it.
jb = serv.JobServer.Jobs[this.strJobName];
Must get my head out of VB mode
-Jamie
Enable/Disable Job with SMO
I am trying to enable/disable a job using a using smo in a script task with the following code
Imports System.Object
Imports Microsoft.SqlServer.Management.Common
Imports Microsoft.SqlServer.Management.Smo
Imports Microsoft.SqlServer.Management.Smo.Agent
Imports Microsoft.SqlServer.Management.Smo.SqlSmoObject
Imports Microsoft.SqlServer.Management.Smo.SmoObjectBase
Imports Microsoft.SqlServer.Management.Smo.NamedSmoObject
Imports Microsoft.SqlServer.Management.Smo.Agent.Job
Imports Microsoft.SqlServer.Management.Smo.Agent.Jobserver
Imports Microsoft.SqlServer.Management.Smo.Agent.AgentObjectBase
Public Class ScriptMain
Public Sub Main()
Dim strJobserver As JobServer
Dim strJob As Job
Dim srv As Server
srv = New Server("conchango-vpc")
strJob = New Job(srv.JobServer, "test")
strJob.IsEnabled = True
strJob.Alter()
Dts.TaskResult = Dts.Results.Success
End Sub
End Class
and i get an error at the alter point.
when code is changed to using the following line
srv.Jobserver.Alter()
it runs successfully but no change is made to the job.
What am I missing?
Ifaka Enefe
Conchango
Instead of: Use:
strJob = New Job(srv.JobServer, "test")
strJob = srv.JobServer.Jobs("test")
I've got the followinng inside a class library:
Server serv; Job jb; serv = new Server(this.strServerName); jb = serv.JobServer.Jobs(this.strJobName); if (strJobEnabledStatus=="True") { jb.IsEnabled = true; } else { jb.IsEnabled=false; } jb.Alter();
And it complains about
serv.JobServer.Jobs(this.strJobName)
Any ideas? I aint much a developer I'm afraid so I'm at a bit of a loss here.
Thanks
Jamie|||s'all right. I've found it.
jb = serv.JobServer.Jobs[this.strJobName];
Must get my head out of VB mode
-Jamie
enable/disable Extende Stored Procedure in MSSQL2005
Hi,
Anybody now how to this programmaticly ? in registry or TSQL statement ?
Have you looked at the Surface Area Configuration tools - the feature configuration controls? That section allows you to disable buckets of XPs that are used by a feature you don't use, but you cannot deactivate only individual XPs in a bucket.
Thanks
Laurentiu
|||if you refer only at running xp_cmdshell , i quote from Books Online
" Introduced in SQL Server 2005, the xp_cmdshell option is a server configuration option that enables system administrators to control whether the xp_cmdshell extended stored procedure can be executed on a system. By default, the xp_cmdshell option is disabled on new installations and can be enabled by using the Surface Area Configuration tool or by running the sp_configure "
for others xp's i didn't find anything
Sunday, February 19, 2012
Enable or disable a relationship between 2 tables at runtime?
Can somebody show me code in how to accomplish this.
ThanksIf you mean foreign key relationship: yes -- see the ForeignKey.IsEnabled property. You can switch FK relationships on and off.
Enable and disable websync.log
Thanks, Pavel
The web sync log should be enabled by default.
On the IE replisapi.dll?diag page, what do you see the status as?
ReplIsapi Settings:
ReplIsapi Settings:
Can you create a new virtual directory and try with that?
Also how did you come into this situation. Did anything change after you created the virtual directory.
|||Yes, I have tried to create virtual directory few times and nothing has changed. I can't realize any change on the server, which could switch off logging.
Another thing is, that we need to monitor production system in which we cannot change virtual directory. In the test enviroment we have not any problems.
|||What about uninstalling and reinstalling the IIS side repl components? Could you try that?|||That's problem, It's production in which a thousands of subscribers are synchronizing and we cannot stop the system. All is working fine, but sometimes, say 1 day in months, there is problem with timeouts on some subscribers and the problem can be repeated on the client side in that moment. So we would like to enable logging in that moment to say, that the timeout is or is not on the server.|||I dont know how you got into this situation, but here is what you can try:
Check if you have this key in your registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Replication\WebSyncLoggingOff
Is this value 1?
If it is, reset it to 0. Then do iisreset.
That should solve your problem
Enable and disable websync.log
Thanks, Pavel
The web sync log should be enabled by default.
On the IE replisapi.dll?diag page, what do you see the status as?
ReplIsapi Settings:
ReplIsapi Settings:
Can you create a new virtual directory and try with that?
Also how did you come into this situation. Did anything change after you created the virtual directory.
|||Yes, I have tried to create virtual directory few times and nothing has changed. I can't realize any change on the server, which could switch off logging.
Another thing is, that we need to monitor production system in which we cannot change virtual directory. In the test enviroment we have not any problems.
|||What about uninstalling and reinstalling the IIS side repl components? Could you try that?|||That's problem, It's production in which a thousands of subscribers are synchronizing and we cannot stop the system. All is working fine, but sometimes, say 1 day in months, there is problem with timeouts on some subscribers and the problem can be repeated on the client side in that moment. So we would like to enable logging in that moment to say, that the timeout is or is not on the server.|||I dont know how you got into this situation, but here is what you can try:
Check if you have this key in your registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Replication\WebSyncLoggingOff
Is this value 1?
If it is, reset it to 0. Then do iisreset.
That should solve your problem