Senaste inläggen 


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

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