Senaste inläggen 


BOL     temp table     Datawarehouse     error     access denied     Activity Monitor     rebuild     sp_MSForEachDB     CU1     features     AcquireConnection     CTE     feedback     clean up     SSIS     security     SQL2008     filter     data warehouse     profile     constraint     Extended Event     T-SQL     sql browser     sp1     SQL Server 2012     SQL server codename Denali     connection     history     undocumented procedures     parallelism     page splits     bugs     XP_cmdshell     resource governor     Cluster     DECIMAL     CTP1     2008     Page life expectancy     package load     virtuell     central management server     SSRS     function     0xC0202009     Trace Flag     dbmail     improve     gratis verktyg     concatenation     transactions     0xC0010014     reorganize index     #am_get_querystats     Säkerhet     Logins     DTA     2005     CMS     connect     CU3     parameters     Business Intelligence     sql 2005     platsannons SQL utvecklare     2011     sql 2008     SQL Server     SQL Denali     SSRS 2008     login error     2000     performance     Reports     HEAP     Microsoft     Techdays     SSAS     HADR     create index

SQL Server errorlog management

Skrivet den 24 februari 2012 i SQL Server best practices, Jan Nieminen, Level 200, sv, en The other day i encountered a problem when trying to open the SQL Server errorlog. SQL Server had been up and running for a long time without a restart so the errorlog had grown very big which made it very time consuming to open. This scenario can be avoided with a litte planning. If you suspect that your SQL Server instance will be running for a long time without interruption it could be a good idea to change the number of errorlogs before it's recycled from default (6) to, for example, 30. But this alone will not be enough. There is a stored procedure to recycle the errorlog, sp_cycle_errorlog which can be used to create a new logfile without restarting SQL Server. This command can be scheduled to run at appropriate intervals and together with the increased number of errorlogs it will make access to your SQL Server errorlog much more painless. These are two very simple things that can make your life a lot easier and they will let you focus on the real problem when it arrives. If you need help with planning your SQL Server environment don't hesitate to contact us.

Skriv en kommentar