[dba-SQLServer] New SQL Server Registration problem

Yeah, EM doesn't provide way of specifying default db.  Therefore the 
default db of login must be changed.

EM suits most of my needs most of the time but sometimes the interface lacks 
one or two things.  The latest example I can think of is specifying a 
password when you backup or restore a db from EM.  That is, if you want to 
backup a db with password option you can't use EM.  Or if you want to 
restore a db from file that has password, you can't use EM.

Billy

>From: Steve Erbach <erbachs at gmail.com>
>Reply-To: dba-sqlserver at databaseadvisors.com
>To: dba-sqlserver at databaseadvisors.com
>Subject: Re: [dba-SQLServer] New SQL Server Registration problem
>Date: Wed, 6 Apr 2005 10:25:09 -0500
>
>Billy,
>
>Hey! Using OSQL to connect to the database (since I could specify the
>default database in the command line) I was, indeed, able to use the
>sp_defaultdb sproc to change the default db. Now -- finally -- I was
>able to connect to the database using Enterprise Manager! Thank you
>very much.
>
>Seems funny, though, that EM doesn't seem to have any built-in way of
>specifying the default db when a new Registration is created. In any
>event, I'm set.
>
>Steve Erbach
>Neenah, WI
>
>On Apr 4, 2005 10:36 PM, Billy Pang <tuxedo_man at hotmail.com> wrote:
> > afaik, you have everything you need to connect to the db.  however, the 
>db
> > login you are using to connect to the SS via EM has a database set as
> > default but the specified user no longer has access to that db.  i'd 
>find
> > some way of setting that default db of that login to a db that login has
> > access to (eg. tempdb).  maybe use the sp_defaultdb sproc.
> >
> > HTH
> >
> > Billy
>_______________________________________________
>dba-SQLServer mailing list
>dba-SQLServer at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
>http://www.databaseadvisors.com
>