SQL Server Trace Flags

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by yusufanis » SQL Server Trace Flags

63 posts, Page 6 of 7

«««3 4 5 6 7 »»

SQL Server Trace Flags

Rate Topic

Display Mode

Topic Options

Author

Message

SQLCharger

Posted Friday, July 06, 2012 6:42 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 7:34 AM
Points: 154, Visits: 1,281

Very nice, keep it coming! Smile

Cheers,

JohnA

Post #1326045

yup

Posted Thursday, July 12, 2012 4:56 PM

SSC Veteran

Group: General Forum Members
Last Login: 2 days ago @ 4:08 AM
Points: 255, Visits: 716

All in place & published now.

Post #1329224

rajasekhar.bollareddy

Posted Wednesday, September 26, 2012 4:57 AM

Forum Newbie

Group: General Forum Members
Last Login: Monday, April 29, 2013 5:59 AM
Points: 3, Visits: 96

Hi,

How can I see default enabled trace flags in Sqlserver..??

Post #1364566

yup

Posted Wednesday, September 26, 2012 5:11 AM

SSC Veteran

Group: General Forum Members
Last Login: 2 days ago @ 4:08 AM
Points: 255, Visits: 716

The command is DBCC TraceStatus.
You can details here
http://msdn.microsoft.com/en-us/library/ms187809.aspx

Post #1364573

Tim-153783

Posted Thursday, October 11, 2012 8:12 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Saturday, May 18, 2013 4:42 PM
Points: 108, Visits: 573

While trace flag -T8038 has been noted, I think it deserves more information.
Hp has a support Document ID: c02110402 that explains it a bit more than the KB article

DESCRIPTION
ProLiant servers that have multiple processor cores and that are running Microsoft SQL Server 2005 SP3 or SQL Server 2008 may stop responding when under a heavy I/O processing load. If Automatic Server Recovery (ASR) is enabled on these servers, the server may reboot when the server stops responding.
SQL Server 2005 SP3 and SQL Server 2008 use mmtimer (Multimedia) timer rather than the RDTSC timer, which changes the clock granularity (to 1ms). This change may result in clock-drift or an unresponsive server if the server uses enhanced power management technologies that change CPU frequencies.
Note: This issue may occur with any ProLiant server that supports power management technologies. Refer to the Affected Platforms included at the bottom of this advisory; however, other platforms may also be affected.
SCOPE
Any ProLiant server that supports power management technologies is running SQL Server 2005 SP3 or SQL Server 2008 on Windows Server 2003.

Post #1371521

rajasekhar.bollareddy

Posted Thursday, October 11, 2012 8:21 AM

Forum Newbie

Group: General Forum Members
Last Login: Monday, April 29, 2013 5:59 AM
Points: 3, Visits: 96

I have implemented fulltext search and Rebuild indexes for this scheduled every 5 mins and its working fine but for every 5 mins of running this job its going to write the below message in SQLServer Error Log.

Message
Changing the status to MERGE for full-text catalog "CatalogName" (7) in database "DbName" (5). This is an informational message only. No user action is required.

How can I avoid this,I mean I do not want to write this into SqlServer Error Log.I have searched for trace flags but I did not find related to this.

Post #1371531

Ron Klimaszewski

Posted Thursday, October 11, 2012 9:52 AM

Valued Member

Group: General Forum Members
Last Login: Today @ 9:38 AM
Points: 69, Visits: 428

This is not the thread to ask these questions.

Find the message number in master..sysmessages and then use sp_altermessage as appropriate.

Post #1371620

yup

Posted Thursday, October 11, 2012 10:58 AM

SSC Veteran

Group: General Forum Members
Last Login: 2 days ago @ 4:08 AM
Points: 255, Visits: 716

Thanks Tim, I'll add those in the next update.

Post #1371686

Rudy Panigas

Posted Tuesday, April 23, 2013 6:45 AM

Old Hand

Group: General Forum Members
Last Login: Today @ 6:36 AM
Points: 306, Visits: 1,015

Great article!!! I would change only one thing to make it easier to ready for all DBA levels. Think if you put the actual version of SQL Server like SQL 2000, SQL 2005, SQL 2008, etc. it would make it a better read. Other than that, it excellent!!

Thanks,

Rudy

Post #1445391

yup

Posted Tuesday, April 23, 2013 7:35 AM

SSC Veteran

Group: General Forum Members
Last Login: 2 days ago @ 4:08 AM
Points: 255, Visits: 716

Trying to keep it as concise as possible.

Post #1445420

« Prev Topic | Next Topic »

63 posts, Page 6 of 7

«««3 4 5 6 7 »»

Permissions