March 8, 2007 at 1:57 pm
Hello,
The situation is this..trying to install sql2kSP4 to a e:\mssql7 (directory) when i do this it creates
e:\mssql7\mssql this is NOT what i want.
But i am thinking this is the default and i am kinda stuck with it. Please help
Thanks
Any suggestions?
Darryl
DHeath
March 8, 2007 at 2:10 pm
Why are you trying to install SQL Server 2000 SP4 to a SQL Server 7 path?
-SQLBill
March 8, 2007 at 2:18 pm
yes that is correct. The reason being is that i am creating a backup server that is identical to the production server and well the path on that is e:\mssql7 so i need to make them the same. It is what it is..
DHeath
March 8, 2007 at 2:24 pm
Then I would accept the default...I think that SQL Server 2000 looks for MSSQL as a folder. So, if it doesn't exist, it has to create one.
-SQLBill
March 8, 2007 at 2:40 pm
Bill,
This i know is true.. but i dont want to accept that... Any ideas or am i just stuck with this situation? I know i can force it elsewhere ..maybe...i think.. hehehe
Thanks for your thoughts
DHeath
March 8, 2007 at 4:18 pm
Is it possible to redirect the registry.. or better just to reinstall starting at sql 7 to reach my goals.
DHeath
March 9, 2007 at 5:11 am
The path you specify during the install is a high-level path. SQL will add additional folders to this path as it sees fit to hold the various SQL components.
SQL2000 likes to add a MSSQL folder. SQL2005 will add this and numerous other folders. Unfortunately, it is the way life works.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
March 9, 2007 at 10:11 am
It sounds like you production server was originally v7.0 and had an upgrade 'in place' performed. In order for you duplicate your production server in every way you will need to perform a v7.0 installation and apply whatever v7.0 SPs that were present then perform an upgrade 'in place'.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
March 9, 2007 at 11:04 am
I'm pretty sure you can't do what you're asking as such - however if you create an unattended install script then it might be possible, I only ever used one of these the once , decided it was too painful, but i figure this is likely the way. I seem to remember that an install will create the file, then all you have to do is take the file and edit it.
No proof you can still do this, just a hazy recollection.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
March 9, 2007 at 11:37 am
Thanks EVERYONE..... but just figured out the real problem... Which is a whole new ball of wax
Trying to install that same SQL 7 instance on a SQL 2k3 server. Which in turn dont support Sql 7. Is there a way and how would i go about making this happen so that i can reach the main goal which is e:\mssql7 housing SQL 2k SP4.
I am not that good with registry to make the changes but not afraid to go there if some one can direct me in that manner.
Thanks
DHeath
March 9, 2007 at 12:52 pm
The only logical way is to start with Windows Server 2000 then:
Not elegant but it will work. I know because we support the hardware and backup for a vendor supplied server that we watched being built in just this way !
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
March 9, 2007 at 2:29 pm
AWESOME!!!!! thanks a TON to everyone that replied.
That worked.. got it going and all...man o man sometimes the obvious is hard to see. Prolly cuz always thinking there has to be an easier way. Thanks again
DHeath
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply