"Ethan Stinar" <estinar@hotmail.com> wrote in message
news:uLrnRjigDHA.1748@TK2MSFTNGP10.phx.gbl...
> To make this short, I'll ask the questions first and outline the problem
> further on:
>
> Can I run two different instances of MS SQL Server on the same physical
> machine using **two different** passwords for the sa account in each
> instance?
>
> If so, can I access both servers with Enterprise Manager using the SQL
> logins or does it require Windows logins?
>
> If not, how would I structure my logins/users to be able to see both
> servers in the same EM Console and or Server Group?
>
> Here's a bit of background:
>
> I am having difficulty running two servers on the same machine. I
> suspect it has to do with the passwords for the sa account. The first
> instance, (local), is SQL 7.0...as I understand it, this is no problem
> as long as the 7.0 server is the local instance. The second server is a
> named instance of SQL 2000. So far so good.
>
> My first attempt was to install SQL 2000 as two different instances and
> then install the app that used 7.0 on the local instance (if it doesn't
> find SQL it auto-installs MSDE). This seemed to work fine as far as SQL
> was concerned. I could connect to both instances and see all the data
> on both. The problem arose when I tried to run the application that
> used the 7.0 instance. It couldn't access--connect to--the server.
> After tracking several installs of the application, I came to realize
> that the problem lay in the sa password.
>
> A dialog that appears toward the end of the install supplies a username
> of sa and a ten-digit password. The install fails if I just click OK.
> However, if I delete the password the install proceeds just fine and the
> dialog tells me the password was not changed. However, the app won't
> connect.
>
> It seems the app is hard-coded to log in as sa under a specific password
> that I have no access to. However, this install process leaves me with
> a blank login for sa.(Fortunately, I will have some influence how this
> is handled in the future)
>
>
> Since this didn't work, I took a different route. I installed the
> aplication first, which installed MSDE/7.0 as the local instance. When
> the user name and password dialog came up during the install, I left it
> as it was. The remaining installation went great and the application
> ran fine afterward.
>
> However, when I tried to install a second instance of SQL (2000 this
> time) I eventually get an error that does not allow me to install the
> new instance if I use sa and a blank password. I am trying to install
> using the system account and a blank password as normal, but this
> doesn't seem to work. (While writing this, I tried again using a third
> instance name and finally got the second server installed...I believe I
> used sa and blank, but when I checked logins in Ent Mgr, the sa account
> has a ten-digit password.)
>
> For the moment, I can work with this. However, I will eventually need
> to have a way to install the 7.0 application on third party(Customer)
> machines that doesn't screw up their system, allows my app to run after
> the install and allows a user login to all servers at once.
>
> So back to my original question...can I use the sa login with unique
> passwords per server or do I have to take a different approach?
>
> As mentiioned above, I have some influence on the developer fo the 7.0
> application, so my gut tells me that to avoid hiccups during a demo
> install, he needs to run the install under sa and a blank password and
> have his script create a different password/SQLlogin for the
> application's default user.
>
> Any feedback would be appreciated.
>
> Thanks
>
> Ethan
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!