Senaste inläggen 


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

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