Senaste inläggen 


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

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