System Center Configuration Manager TechCenter >
System Center Configuration Manager Forums
>
Configuration Manager Setup/Deployment
>
ConfigMgr SP2 TESTDBUPGRADE syntax
ConfigMgr SP2 TESTDBUPGRADE syntax
- I've seen this question posted on a few public forums, but never an answer or reply.
Can the /TESTDBUPGRADE option of the SP2 setup program operate against a named SQL 2005 instance?
If so, what is the correct syntax for specifying the named instance? We've tried a variety of combinations and workarounds, including SQL aliases, to no avail.
And if someone can provide an authoritative "No" answer to the question, can we get this restriction highlighted in the documentation, up front, so folks don't burn cycles building unusable test SQL instances? Though it would be preferable to allow it.
Bleah.
Jeff Kantner
Answers
I tried a lot to perform testdbupgrade using SQL instance, but no luck. looks like it is not supported as i did not find any details about performing testdbupgrade using SQL Instance.
So its better use default instance SQL server to perform testdbupgrade.
Surendar Reddy- Proposed As Answer byReddy Surendar Tuesday, November 10, 2009 10:08 PM
- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorMonday, November 16, 2009 3:50 AM
All Replies
- Hi Jeff,
Can you try /testdbupgrade <DB Name>
This should be able to identify SQL instance and DB to perform TESTDBUPGRADE.
Surendar Reddy - Tried that. No go. Altogether we tried
setup /TESTDBUPGRADE dbname
setup /TESTDBUPGRADE instance\dbname
setup /TESTDBUPGRADE server\instance\dbname
setup /TESTDBUPGRADE server\dbname
setup /TESTDBUPGRADE server\instance.dbname
setup /TESTDBUPGRADE alias\dbname
setup /TESTDBUPGRADE alias
In every case, we got exactly the same result:
08001 “SQL Server does not exist or access denied"
However, there was no reference in the SQL logs of an access (successful or denied), so I think it was a "no find" not an actual denial.
By now, I've ripped down the SQL, reinstalled it to a default instance, upgraded to SP2, restored by backup DB (this is about a 3-hr exercise in our none-too-robust test environment). After which, /TESTDBUPGRADE ran like a charm.
So count me as convinced that running /TESTDBUPGRADE on a named instance is not supported. Just wish I'd've known in advance. Would've saved a couple days.
Jeff Kantner May be you already know, but just want to clear that, while running a command testdbupgrade should be in lower case. hope you are doing that.
Abhishek Joshi http://blogcastrepository.com/blogs/abi/default.aspx http://blogcastrepository.com/members/Abhishek.aspx- Hi,
If it were true, that would be an odd restriction, inasmuch as the help screen you get from setup /? shows the parameter in uppercase as /TESTDBUPGRADE.
But I don't think it's true (or at least, enforced), since when we did finally succeed (using a default SQL instance) we also used /TESTDBUPGRADE in uppercase.
Jeff Kantner I tried a lot to perform testdbupgrade using SQL instance, but no luck. looks like it is not supported as i did not find any details about performing testdbupgrade using SQL Instance.
So its better use default instance SQL server to perform testdbupgrade.
Surendar Reddy- Proposed As Answer byReddy Surendar Tuesday, November 10, 2009 10:08 PM
- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorMonday, November 16, 2009 3:50 AM
