Showing posts with label trace. Show all posts
Showing posts with label trace. Show all posts

Wednesday, March 7, 2012

Deferred Updates (Singleton Updates)

How is deferred update implemented in SQL 2005 Replication? I have tried to
set the trace flag 8207 like in SQL 2000, but this is not working.
Thanks,
Andrew
MCSA,MCDBA
Hi Andrew - I've just tried adding the trace flag and it is added OK as
confirmed by "dbcc tracestatus". Did you have a problem adding it or was the
problem later on?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Friday, February 17, 2012

Default Trace SQL 2005

What settings are there for the default trace option in SQL 2005? I see that
it stores a history of traces in the \MSSQL.1\MSSQL\LOG. It is pretty cool
because it will show you in SSMS a SQL report with schema changes on a per
database level.
I just want to know how to modify the setings for the default trace option as
far as size, time, and rollover.The only setting that exists is to turn it off (using sp_configure). IF you want something different
from the default, you have to roll your own (using server-side traces). Being able to customize
these things is interesting, so you might want to suggest this for next version
(http://connect.microsoft.com/sqlserver).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"evan4434" <u36821@.uwe> wrote in message news:7709e496ca18a@.uwe...
> What settings are there for the default trace option in SQL 2005? I see that
> it stores a history of traces in the \MSSQL.1\MSSQL\LOG. It is pretty cool
> because it will show you in SSMS a SQL report with schema changes on a per
> database level.
> I just want to know how to modify the setings for the default trace option as
> far as size, time, and rollover.
>