Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 953144 - Last Review: May 22, 2008 - Revision: 1.0
When you run the Setup program to upgrade a SMS 2003 site database to run System Center Configuration Manager 2007, Setup logging may slow
Consider the following scenario:
- You run the Setup program to upgrade a Microsoft System Management Server (SMS) 2003 site database to run Microsoft System Center Configuration Manager 2007 or System Center Configuration Manager 2007 with Service Pack 1 (SP1).
- You run the Setup program together with the /testdbupgrade switch or with the /upgrade switch.
In this scenario, Setup logging may slow or may appear unresponsive.
This problem occurs when a schema change is implemented in very large tables in the Microsoft SQL Server database. Processing time varies depending on how much inventory data is stored in the database and on the hardware that is used to host the instance of SQL Server.
Note The Setup.exe process can be monitored to make sure that the upgrade is still in progress.
To work around this problem, follow these steps before you run the Setup program together with the
/testdbupgrade switch or with the
/upgrade switch.
Note This workaround improves the runtime of the Setup program when it is used together with these switches. This workaround does not actually fix any problems in the site database itself.
- Click Start, click All Programs, click Microsoft SQL Server 2005, and then click SQL Server Management Studio.
- Connect to the server on which the database exists.
- Click New Query, and then select the database on which you want to run the /testdbupgrade switch.
- Paste the following script in the query window.
declare @TName varchar(255)
declare Inv cursor local fast_forward for
select SpecificTableName from GroupMap
open Inv
fetch next from Inv into @TName
while @@FETCH_STATUS=0
begin
if OBJECT_ID(@TName) is not NULL and COLUMNPROPERTY(OBJECT_ID(@TName),'rowversion','ColumnId') is NULL
begin
print 'Adding rowversion to table ' + @TName
exec('alter table ' + @TName + ' add [rowversion] rowversion not null')
end
else
print 'Rowversion already on table ' + @TName
fetch next from Inv into @TName
end
close Inv
deallocate Inv
- Click Execute.
- Run the SMS Setup program together with the /testdbupgrade switch or with the /upgrade switch.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
When you upgrade to System Center Configuration Manager 2007, make sure that available disk space is at least two and a half times the size of the site database. This space is required for the database upgrade to succeed.
APPLIES TO
- Microsoft Systems Management Server 2003
- Microsoft System Center Configuration Manager 2007
| kbtshoot kbcode kbpubtypekc kbprb KB953144 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate