"BayCoMIS" <BayCo***@discussions.microsoft.com> wrote in message
news:80DC3B08-92DF-46C5-A697-9566F5159404@microsoft.com...
> Let me preface by saying that I'm not a DBA-type person.  I'm more of the
> network guy who truly hopes to have an honest-to-God DBA hired on within
> the
> next six months.  I'm the interim DBA without much DBA knowledge just
> backing
> up databases as best I can.
>
> For pure political reasons, I must allow a non-IT person access to
> Enterprise Manager for a SQL 2005 database within their subnet.  (Scary,
> to
> say the least.)  The main reason is that they want to be able to backup
> their
> own database whenever they see fit -- scheduling be damned!  The software
> vendor does not offer a backup within their own software; Enterprise
> Manager
> must be used -- with full admin privileges of the SQL Server!!!
>
> I want to be able to prevent the user from accessing any of the other SQL
> databases (2000 & 2005) within the domain.  Is this possible?  If so, how?
> Can someone point me in the right direction?
>
> I'd much prefer a script of some kind to allow the user to run a SQL
> backup
> of the database without invoking Enterprise Manager at all.  Is THIS
> possible?
>
> My sanity begs for help.  Thanks in advance to whomever can offer
> assistance
> with this issue.

"Geoff N. Hiten" wrote:

> First,  Enterprise Manager does not work with SQL 2005.  You have to use the
> new SQL Server Management Studio.  SSMS does work with SQL 2000 and SQL
> 2005.
>
> Second, why don't you write a short backup script using the SQLCMD utility
> that he can invoke to create a backup, you do not have to start a backup
> using a GUI.  Alternatively, with transaction log backups and FULL recovery,
> he can recover to any point in time with the scheduled full restore as the
> starting point.  Therefore he has no need to create random backups.
>
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
>
>
> "BayCoMIS" <BayCo***@discussions.microsoft.com> wrote in message
> news:80DC3B08-92DF-46C5-A697-9566F5159404@microsoft.com...
> > Let me preface by saying that I'm not a DBA-type person.  I'm more of the
> > network guy who truly hopes to have an honest-to-God DBA hired on within
> > the
> > next six months.  I'm the interim DBA without much DBA knowledge just
> > backing
> > up databases as best I can.
> >
> > For pure political reasons, I must allow a non-IT person access to
> > Enterprise Manager for a SQL 2005 database within their subnet.  (Scary,
> > to
> > say the least.)  The main reason is that they want to be able to backup
> > their
> > own database whenever they see fit -- scheduling be damned!  The software
> > vendor does not offer a backup within their own software; Enterprise
> > Manager
> > must be used -- with full admin privileges of the SQL Server!!!
> >
> > I want to be able to prevent the user from accessing any of the other SQL
> > databases (2000 & 2005) within the domain.  Is this possible?  If so, how?
> > Can someone point me in the right direction?
> >
> > I'd much prefer a script of some kind to allow the user to run a SQL
> > backup
> > of the database without invoking Enterprise Manager at all.  Is THIS
> > possible?
> >
> > My sanity begs for help.  Thanks in advance to whomever can offer
> > assistance
> > with this issue.
>
>
>

"BayCoMIS" <BayCo***@discussions.microsoft.com> wrote in message
news:3DCE1CE9-524E-4610-A60D-999E080A7CA0@microsoft.com...
> Geoff,
>
> Thanks for the scripting advice.  Unfortunately, I don't know much about
> SQLCMD scripting.  So, my next (obvoius) question would be:
>
> Is it possible to write a script that one could run from a workstation and
> NOT have SSMS installed on that workstation?   Can we Share out the
> directories in which the database and transaction logs are located
> (READ-ONLY, of course) and have a script run from the workstation so that
> we
> don't have to have SSMS installed for the user?
>
> Thanks again for your help.  I've been researching the SQLCMD and trying
> to
> get a grip on it.
>
>
> "Geoff N. Hiten" wrote:
>
>> First,  Enterprise Manager does not work with SQL 2005.  You have to use
>> the
>> new SQL Server Management Studio.  SSMS does work with SQL 2000 and SQL
>> 2005.
>>
>> Second, why don't you write a short backup script using the SQLCMD
>> utility
>> that he can invoke to create a backup, you do not have to start a backup
>> using a GUI.  Alternatively, with transaction log backups and FULL
>> recovery,
>> he can recover to any point in time with the scheduled full restore as
>> the
>> starting point.  Therefore he has no need to create random backups.
>>
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>>
>>
>> "BayCoMIS" <BayCo***@discussions.microsoft.com> wrote in message
>> news:80DC3B08-92DF-46C5-A697-9566F5159404@microsoft.com...
>> > Let me preface by saying that I'm not a DBA-type person.  I'm more of
>> > the
>> > network guy who truly hopes to have an honest-to-God DBA hired on
>> > within
>> > the
>> > next six months.  I'm the interim DBA without much DBA knowledge just
>> > backing
>> > up databases as best I can.
>> >
>> > For pure political reasons, I must allow a non-IT person access to
>> > Enterprise Manager for a SQL 2005 database within their subnet.
>> > (Scary,
>> > to
>> > say the least.)  The main reason is that they want to be able to backup
>> > their
>> > own database whenever they see fit -- scheduling be damned!  The
>> > software
>> > vendor does not offer a backup within their own software; Enterprise
>> > Manager
>> > must be used -- with full admin privileges of the SQL Server!!!
>> >
>> > I want to be able to prevent the user from accessing any of the other
>> > SQL
>> > databases (2000 & 2005) within the domain.  Is this possible?  If so,
>> > how?
>> > Can someone point me in the right direction?
>> >
>> > I'd much prefer a script of some kind to allow the user to run a SQL
>> > backup
>> > of the database without invoking Enterprise Manager at all.  Is THIS
>> > possible?
>> >
>> > My sanity begs for help.  Thanks in advance to whomever can offer
>> > assistance
>> > with this issue.
>>
>>
>>

"BayCoMIS" <BayCo***@discussions.microsoft.com> wrote in message
news:3DCE1CE9-524E-4610-A60D-999E080A7CA0@microsoft.com...
> Geoff,
>
> Thanks for the scripting advice.  Unfortunately, I don't know much about
> SQLCMD scripting.  So, my next (obvoius) question would be:
>
> Is it possible to write a script that one could run from a workstation and
> NOT have SSMS installed on that workstation?   Can we Share out the
> directories in which the database and transaction logs are located
> (READ-ONLY, of course) and have a script run from the workstation so that we
> don't have to have SSMS installed for the user?
>
> Thanks again for your help.  I've been researching the SQLCMD and trying to
> get a grip on it.
>
>
> "Geoff N. Hiten" wrote:
>
>> First,  Enterprise Manager does not work with SQL 2005.  You have to use the
>> new SQL Server Management Studio.  SSMS does work with SQL 2000 and SQL
>> 2005.
>>
>> Second, why don't you write a short backup script using the SQLCMD utility
>> that he can invoke to create a backup, you do not have to start a backup
>> using a GUI.  Alternatively, with transaction log backups and FULL recovery,
>> he can recover to any point in time with the scheduled full restore as the
>> starting point.  Therefore he has no need to create random backups.
>>
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>>
>>
>> "BayCoMIS" <BayCo***@discussions.microsoft.com> wrote in message
>> news:80DC3B08-92DF-46C5-A697-9566F5159404@microsoft.com...
>> > Let me preface by saying that I'm not a DBA-type person.  I'm more of the
>> > network guy who truly hopes to have an honest-to-God DBA hired on within
>> > the
>> > next six months.  I'm the interim DBA without much DBA knowledge just
>> > backing
>> > up databases as best I can.
>> >
>> > For pure political reasons, I must allow a non-IT person access to
>> > Enterprise Manager for a SQL 2005 database within their subnet.  (Scary,
>> > to
>> > say the least.)  The main reason is that they want to be able to backup
>> > their
>> > own database whenever they see fit -- scheduling be damned!  The software
>> > vendor does not offer a backup within their own software; Enterprise
>> > Manager
>> > must be used -- with full admin privileges of the SQL Server!!!
>> >
>> > I want to be able to prevent the user from accessing any of the other SQL
>> > databases (2000 & 2005) within the domain.  Is this possible?  If so, how?
>> > Can someone point me in the right direction?
>> >
>> > I'd much prefer a script of some kind to allow the user to run a SQL
>> > backup
>> > of the database without invoking Enterprise Manager at all.  Is THIS
>> > possible?
>> >
>> > My sanity begs for help.  Thanks in advance to whomever can offer
>> > assistance
>> > with this issue.
>>
>>
>>

"Tibor Karaszi" wrote:

> You can download a redistribution of SQLCMD from
> http://www.microsoft.com/downloads/details.aspx?FamilyID=df0ba5aa-b4bd-4705-aa0a-b477ba72a9cb&DisplayLang=en
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
>
> "BayCoMIS" <BayCo***@discussions.microsoft.com> wrote in message
> news:3DCE1CE9-524E-4610-A60D-999E080A7CA0@microsoft.com...
> > Geoff,
> >
> > Thanks for the scripting advice.  Unfortunately, I don't know much about
> > SQLCMD scripting.  So, my next (obvoius) question would be:
> >
> > Is it possible to write a script that one could run from a workstation and
> > NOT have SSMS installed on that workstation?   Can we Share out the
> > directories in which the database and transaction logs are located
> > (READ-ONLY, of course) and have a script run from the workstation so that we
> > don't have to have SSMS installed for the user?
> >
> > Thanks again for your help.  I've been researching the SQLCMD and trying to
> > get a grip on it.
> >
> >
> > "Geoff N. Hiten" wrote:
> >
> >> First,  Enterprise Manager does not work with SQL 2005.  You have to use the
> >> new SQL Server Management Studio.  SSMS does work with SQL 2000 and SQL
> >> 2005.
> >>
> >> Second, why don't you write a short backup script using the SQLCMD utility
> >> that he can invoke to create a backup, you do not have to start a backup
> >> using a GUI.  Alternatively, with transaction log backups and FULL recovery,
> >> he can recover to any point in time with the scheduled full restore as the
> >> starting point.  Therefore he has no need to create random backups.
> >>
> >> --
> >> Geoff N. Hiten
> >> Senior Database Administrator
> >> Microsoft SQL Server MVP
> >>
> >>
> >>
> >>
> >> "BayCoMIS" <BayCo***@discussions.microsoft.com> wrote in message
> >> news:80DC3B08-92DF-46C5-A697-9566F5159404@microsoft.com...
> >> > Let me preface by saying that I'm not a DBA-type person.  I'm more of the
> >> > network guy who truly hopes to have an honest-to-God DBA hired on within
> >> > the
> >> > next six months.  I'm the interim DBA without much DBA knowledge just
> >> > backing
> >> > up databases as best I can.
> >> >
> >> > For pure political reasons, I must allow a non-IT person access to
> >> > Enterprise Manager for a SQL 2005 database within their subnet.  (Scary,
> >> > to
> >> > say the least.)  The main reason is that they want to be able to backup
> >> > their
> >> > own database whenever they see fit -- scheduling be damned!  The software
> >> > vendor does not offer a backup within their own software; Enterprise
> >> > Manager
> >> > must be used -- with full admin privileges of the SQL Server!!!
> >> >
> >> > I want to be able to prevent the user from accessing any of the other SQL
> >> > databases (2000 & 2005) within the domain.  Is this possible?  If so, how?
> >> > Can someone point me in the right direction?
> >> >
> >> > I'd much prefer a script of some kind to allow the user to run a SQL
> >> > backup
> >> > of the database without invoking Enterprise Manager at all.  Is THIS
> >> > possible?
> >> >
> >> > My sanity begs for help.  Thanks in advance to whomever can offer
> >> > assistance
> >> > with this issue.
> >>
> >>
> >>
>
>
>

"BayCoMIS" <BayCo***@discussions.microsoft.com> wrote in message
news:48648645-33C7-4EC8-B387-D8C6680AD193@microsoft.com...
> Thanks for the link!  You're a mind-reader...  finding a redist of SQLCMD was
> going to be my next question.
>
> By the way, is there any tweak one can perform to gray out (remove) the
> "Remember password" option when running SSMS?  We have to use SQL Server
> Authentication, and I'd like to force the issue of requiring the user to log
> on each time.
>
> Thanks again for the link, Tibor.
>
>
> "Tibor Karaszi" wrote:
>
>> You can download a redistribution of SQLCMD from
>> http://www.microsoft.com/downloads/details.aspx?FamilyID=df0ba5aa-b4bd-4705-aa0a-b477ba72a9cb&DisplayLang=en
>>
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>>
>> "BayCoMIS" <BayCo***@discussions.microsoft.com> wrote in message
>> news:3DCE1CE9-524E-4610-A60D-999E080A7CA0@microsoft.com...
>> > Geoff,
>> >
>> > Thanks for the scripting advice.  Unfortunately, I don't know much about
>> > SQLCMD scripting.  So, my next (obvoius) question would be:
>> >
>> > Is it possible to write a script that one could run from a workstation and
>> > NOT have SSMS installed on that workstation?   Can we Share out the
>> > directories in which the database and transaction logs are located
>> > (READ-ONLY, of course) and have a script run from the workstation so that we
>> > don't have to have SSMS installed for the user?
>> >
>> > Thanks again for your help.  I've been researching the SQLCMD and trying to
>> > get a grip on it.
>> >
>> >
>> > "Geoff N. Hiten" wrote:
>> >
>> >> First,  Enterprise Manager does not work with SQL 2005.  You have to use the
>> >> new SQL Server Management Studio.  SSMS does work with SQL 2000 and SQL
>> >> 2005.
>> >>
>> >> Second, why don't you write a short backup script using the SQLCMD utility
>> >> that he can invoke to create a backup, you do not have to start a backup
>> >> using a GUI.  Alternatively, with transaction log backups and FULL recovery,
>> >> he can recover to any point in time with the scheduled full restore as the
>> >> starting point.  Therefore he has no need to create random backups.
>> >>
>> >> --
>> >> Geoff N. Hiten
>> >> Senior Database Administrator
>> >> Microsoft SQL Server MVP
>> >>
>> >>
>> >>
>> >>
>> >> "BayCoMIS" <BayCo***@discussions.microsoft.com> wrote in message
>> >> news:80DC3B08-92DF-46C5-A697-9566F5159404@microsoft.com...
>> >> > Let me preface by saying that I'm not a DBA-type person.  I'm more of the
>> >> > network guy who truly hopes to have an honest-to-God DBA hired on within
>> >> > the
>> >> > next six months.  I'm the interim DBA without much DBA knowledge just
>> >> > backing
>> >> > up databases as best I can.
>> >> >
>> >> > For pure political reasons, I must allow a non-IT person access to
>> >> > Enterprise Manager for a SQL 2005 database within their subnet.  (Scary,
>> >> > to
>> >> > say the least.)  The main reason is that they want to be able to backup
>> >> > their
>> >> > own database whenever they see fit -- scheduling be damned!  The software
>> >> > vendor does not offer a backup within their own software; Enterprise
>> >> > Manager
>> >> > must be used -- with full admin privileges of the SQL Server!!!
>> >> >
>> >> > I want to be able to prevent the user from accessing any of the other SQL
>> >> > databases (2000 & 2005) within the domain.  Is this possible?  If so, how?
>> >> > Can someone point me in the right direction?
>> >> >
>> >> > I'd much prefer a script of some kind to allow the user to run a SQL
>> >> > backup
>> >> > of the database without invoking Enterprise Manager at all.  Is THIS
>> >> > possible?
>> >> >
>> >> > My sanity begs for help.  Thanks in advance to whomever can offer
>> >> > assistance
>> >> > with this issue.
>> >>
>> >>
>> >>
>>
>>
>>

"Erland Sommarskog" wrote:

> BayCoMIS (BayCo***@discussions.microsoft.com) writes:
> > For pure political reasons, I must allow a non-IT person access to
> > Enterprise Manager for a SQL 2005 database within their subnet.  (Scary,
> > to say the least.)  The main reason is that they want to be able to
> > backup their own database whenever they see fit -- scheduling be damned!
> >  The software vendor does not offer a backup within their own software;
> > Enterprise Manager must be used -- with full admin privileges of the SQL
> > Server!!!
> 
> To add to Geoff's respons: you don't need full admin rights to backup a
> single database. It's sufficient to have db_owner rights on that
> database.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>