SQL Server 2005 sp2 and maintenance plan (bug)

Hello everyone,

Hope I post at the rigth place.

Last week we applied service pack 2 on our SQL Server 2005 64-bit. We are now at the version (SELECT @@version):

Microsoft SQL Server 2005 - 9.00.3042.00 (X64)

Since then, we have 2 maintenance plans that fails:

- Rebuild indexes

- Update statistcs

For the update statiscs job, here is the output we can see as output in the LOG folder:

NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3042
Report was generated on "sql5".
Maintenance Plan: Regnr les statistiques
Duration: 00:44:59
Status: Succeeded.
Details:

And this error on the window when we execute the maintenance plan live:

Execute Maintenance Plan

- Execute maintenance plan. Regnr les statistiques (Error)

Messages

Execution failed. See the maintenance plan and SQL Server Agent job history logs for details.

ADDITIONAL INFORMATION:

Job 'Regnr les statistiques.Subplan_1' failed. (SqlManagerUI)

What seems more like a bug to me is when I try to create a new maintenance plan using a rebuild index task in the plan. I edit that task, click on the View T-SQL button then I click on the close button of the Transact-SQL (task generated) window and then I receive the following error:

===================================

Rebuild failed for Index 'idx1'. (Microsoft.SqlServer.Smo)


For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Rebuild+Index&LinkId=20476


Program Location:

at Microsoft.SqlServer.Management.Smo.Index.RebuildImpl(Boolean allIndexes)
at Microsoft.SqlServer.Management.Smo.Index.Rebuild()
at Microsoft.SqlServer.Management.DatabaseMaintenance.DBMaintTaskReindexForm.RebuildIndex(Index index, Int32 serverVersion)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DBMaintTaskReindexForm.BuildScript()

===================================

Le thread a t abandonn. (System.Data)


Program Location:

at SNINativeMethodWrapper.SNIPacketGetConnection(IntPtr packet)
at System.Data.SqlClient.TdsParserStateObject.ProcessSniPacket(IntPtr packet, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteReader(String sqlCommand)
at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataReader(String query)
at Microsoft.SqlServer.Management.Smo.DataProvider.SetConnectionAndQuery(ExecuteSql execSql, String query)
at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataProvider(StringCollection query, Object con, StatementBuilder sb, RetriveMode rm)
at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillData(ResultType resultType, StringCollection sql, Object connectionInfo, StatementBuilder sb)
at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillDataWithUseFailure(SqlEnumResult sqlresult, ResultType resultType)
at Microsoft.SqlServer.Management.Smo.SqlObjectBase.BuildResult(EnumResult result)
at Microsoft.SqlServer.Management.Smo.SqlObjectBase.GetData(EnumResult erParent)
at Microsoft.SqlServer.Management.Smo.Environment.GetData()
at Microsoft.SqlServer.Management.Smo.Environment.GetData(Request req, Object ci)
at Microsoft.SqlServer.Management.Smo.Enumerator.GetData(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.Smo.ExecutionManager.GetEnumeratorDataReader(Request req)
at Microsoft.SqlServer.Management.Smo.SqlSmoObject.GetInitDataReader(String[] fields, OrderBy[] orderby)
at Microsoft.SqlServer.Management.Smo.SqlSmoObject.ImplInitialize(String[] fields, OrderBy[] orderby)
at Microsoft.SqlServer.Management.Smo.SqlSmoObject.Initialize(Boolean allProperties)
at Microsoft.SqlServer.Management.Smo.SqlSmoObject.OnPropertyMissing(String propname)
at Microsoft.SqlServer.Management.Smo.SqlSmoObject.GetPropValueOptional(String propName)
at Microsoft.SqlServer.Management.Smo.Index.HasXmlColumn(ScriptingOptions so, Boolean throwIfNotSet)
at Microsoft.SqlServer.Management.Smo.Index.RebuildImpl(Boolean allIndexes)

Whats wrong we that sp?

Regards.

Carl

[6847 byte] By [CarlBruneau] at [2008-1-2]
# 1

We are investigating the first of the issues you cite, and will make a call on when to fix it.

For the second, I am under the impression that this is a UI only failure, and that the task runs well at runtime. I believe also this repros only when you close the dialog while it is thinking about what script to provide. If this is the case, we likely wouldn't fix this till our next major release.

Let me know if I am confused.

jkh

JamesK.Howey-MSFT at 2007-9-13 > top of Msdn Tech,SQL Server,SQL Server SMO/DMO...
# 2

Hello James,

The first issue has been solved by passing to version 9.00.3152.00.

The second issue is not an irritating at all. It is just that the window is trying to generate the underlying SQL but we click on the cancel button before it finish and the exception arise.

Best regards,

Carl

CarlBruneau at 2007-9-13 > top of Msdn Tech,SQL Server,SQL Server SMO/DMO...

SQL Server

Site Classified