nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I disable MSSQL server for TS?

Bowker

I would like to STOP using MSSQL for event logging in TS. How do I disable it?

It's currently throwing errors (LOTS of them) and we don't use it so I want to disable it.

Find more posts tagged with

Comments

Corey_Null

Do you just want to disable the event subsystem? If so, I think that you can just change the following setting in the iw-home\etc\iw.cfg file to "false":

[event_subsystem]
ew_enable=true

I think that you need to issue an iwreset -ui after that.

Maybe stop the Interwoven Event Subsystem service and disable it?

You could go as far as to remove the drivers from iw-home\eventsubsystem\lib, remove the database config section in iw-home\eventsubsystem\conf\jsmconfignew.xml or configure the event subsystem to use some other database like MySQL or Oracle.

Migrateduser

Besides the sugessted parameter, turn the service to manual.

Be warned that you will loose the update document reflection in the search and also you need to manually cleanup the workflow jobs from the backing store.

Most likely the errors you are getting in the logs with the mssql are deadlock related. There is a KB in the support site which suggests simple steps to get this fixed. Anyone number ? or search something loke "sqlserver deadlocks"

Better to start with the fresh databse as it might have grown by now.

Migrateduser

Heres the script.
exec sp_rename @objname='messages',
@newname='messages_table', @objtype =
'OBJECT'
exec sp_rename @objname='message_handles',
@newname='message_handles_table',
@objtype='OBJECT'

create view messages
as
select * from messages_table with(nolock)

go

create view message_handles
as
select * from message_handles_table with(nolock)

go

Stop the eventSubsystem.
Run this on the eventSubsystem database and for better results delete all the entries in the messages and messages_handles table (else there will be lot of piled up events delivered).

ISCBorisB

Be warned that you will loose the update document reflection in the search and also you need to manually cleanup the workflow jobs from the backing store

Just a little side note. Boker's indicated version is 6.5 so Workflows are wft's. Therefore terminated WF clean-up will work with or without event Service

Corey_Null

Here are the threads that I used (although I don't seem to be logging to the db -see other thread):

http://devnet.interwoven.com/forums_vb/showthread.php?t=15590&forumid=11

http://sourceforge.net/tracker/index.php?func=detail&aid=934627&group_id=54559&atid=474136

http://devnet.interwoven.com/forums_vb/showthread.php?t=10165&forumid=11

http://devnet.interwoven.com/forums_vb/showthread.php?p=76567 This one is on the deadlock issue. I had to run the query in 2 parts because I was getting an error that said something to the effect of Create View had to be at the beginning, so that is where I split it. I first ran:

exec sp_rename @objname='messages',
@newname='messages_table', @objtype =
'OBJECT'
exec sp_rename @objname='message_handles',
@newname='message_handles_table',
@objtype='OBJECT'

Then:

create view messages
as
select * from messages_table with(nolock)

go

create view message_handles
as
select * from message_handles_table with(nolock)

go

Migrateduser

>>This one is on the deadlock issue. I had to run the query in 2 parts because I was getting an error that said something to the effect of Create View had to be at the beginning, so that is where I split it. I first ran:

hmm .. look for the KB in the support site for the sqlserver deadlocks. The script there can be run in one go.
Even running in the two parts is ok (essentially the same Smiley Happy

)