Does SQL degrade when DBCC Traceon 1222 is switched on?

Hi,

I'm seeing a few deadlocks on my SQL 2005 production database and wondered what i could expect if i switch on the trace flag 1222. Can this cause more deadlocks to occur? Will the performance of SQL degrade? Is it safe to have this flag set on a production server or is there another method you would recommend?

Thanks

Martin

In general every extra logging causes a little performance impact but it will not cause extra deadlocks. The performance impact is more acceptable than having deadlocks so until you have found the root cause of these deadlocks I would not hesitate to use the trace flag.

Do not bother too much about the performance impact however, it is very little and definitely less than the cost of having deadlocks.

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

Does SQL degrade when DBCC Traceon 1222 is switched on?

Hi,

I'm seeing a few deadlocks on my SQL 2005 production database and wondered what i could expect if i switch on the trace flag 1222. Can this cause more deadlocks to occur? Will the performance of SQL degrade? Is it safe to have this flag set on a production server or is there another method you would recommend?

Thanks

Martin

In general every extra logging causes a little performance impact but it will not cause extra deadlocks. The performance impact is more acceptable than having deadlocks so until you have found the root cause of these deadlocks I would not hesitate to use the trace flag.

Do not bother too much about the performance impact however, it is very little and definitely less than the cost of having deadlocks.

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

sql

Does SQL 2005 still support the *= syntax?

Does SQL Server 2005 still support the *= outer join syntax without having
to set the DB Compatibility switch? A friend of mine tested out SQL 2005
Beta 2 and said that *= was still supported, but then when the official SQL
2005 release came out, *= no longer worked without having to set the
compatibility switch. That seems like a HUGE change to make between the
last beta and the official release.AFAIK, this change was made around the June CTP timeframe. The answer is
no, there is no support for *= unless you're in 8.0 compatability mode (or
lower). Which, IMHO, is a great thing. That syntax has caused so many
problems over the years...
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"Jay Sullivan" <jaysullivan@.nospam.nospam> wrote in message
news:e42BOS74FHA.2560@.TK2MSFTNGP12.phx.gbl...
> Does SQL Server 2005 still support the *= outer join syntax without having
> to set the DB Compatibility switch? A friend of mine tested out SQL 2005
> Beta 2 and said that *= was still supported, but then when the official
> SQL 2005 release came out, *= no longer worked without having to set the
> compatibility switch. That seems like a HUGE change to make between the
> last beta and the official release.
>