Senaste inläggen 

Taggar 

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

Running COM objects outside SQL Server process

Skrivet den 31 juli 2012 i Level 400, SQL Server allmänt, Steinar Andersen, Nivå, sv, en

In some cases, you can get an error 0x00000005 (Access Violation) in the SQL Server process, that is caused by running external COM objects via sp_OAcreate. The effect is that the entire SQL server process rolls over and dies immedeately.

This can be quite hard to solve without the help of Microsoft PSS, but there is one thing you can try that might help. When you call sp_OAcreate, use option 4, wich will spawn teh COM object in a process outside the SQL server process. If and when that process crashes, atleast it will not take down the entire SQL Server process with it.

Read more about sp_OAcreate at http://msdn.microsoft.com/en-us/library/ms189763(v=sql.105).aspx

Skriv en kommentar