For security reasons I dropped xp_cmdshell from my master database. Now
I find that I need it once again... is there a way to restore it or
somehow copy it from another database server? I've tried to use
enterprise manager to DTS it over but I can't DTS anything from the
master database. Is there any other way?
Thanks in advance.
Rsto create it back use the following and let know if it works:
Use Master
sp_addextendedproc xp_cmdshell, 'xplog70.dll'
Showing posts with label security. Show all posts
Showing posts with label security. Show all posts
Sunday, March 11, 2012
deleted xp_cmdshell... how do I restore it?
For security reasons I dropped xp_cmdshell from my master database. Now
I find that I need it once again... is there a way to restore it or
somehow copy it from another database server? I've tried to use
enterprise manager to DTS it over but I can't DTS anything from the
master database. Is there any other way?
Thanks in advance.
Rsto create it back use the following and let know if it works:
Use Master
sp_addextendedproc xp_cmdshell, 'xplog70.dll'
I find that I need it once again... is there a way to restore it or
somehow copy it from another database server? I've tried to use
enterprise manager to DTS it over but I can't DTS anything from the
master database. Is there any other way?
Thanks in advance.
Rsto create it back use the following and let know if it works:
Use Master
sp_addextendedproc xp_cmdshell, 'xplog70.dll'
Wednesday, March 7, 2012
deleted AD
I am not a DBA and may have a problem. I am running an
app that sits on top of the sql desktop engine. I am
using AD integrated security. My problem is that one of
the domain admins decided to reformat and reinstall both
our AD servers.(#$%#) There is a new domain, but there is
no longer an AD server for the account that "owns" the
sql database.
I am still logged in to the server with the account that
owns the database. I have not logged out since the AD was
deleted for fear that my database will no longer be
accessible. As far as I can see, the admin tools
available to me for the desktop engine don't have the
ability to change the owner of the database.
What must I do to ensure that I can access this database?You can change the database owner with sp_changedbowner. Run this using the
command-line OSQL utility like the example below:
OSQL -Q "EXEC sp_changedbowner 'sa'" -d MyDatabase -E -S MyServer
By default, members of the local Administrators have sysadmin access to SQL
Server via the 'BULTIN\Administrators' login. This will provide sysadmin
access to your SQL Server instance as long as you can access the machine
with Windows account that is a member of the local Administrators group.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"hhtpnoc" <anonymous@.discussions.microsoft.com> wrote in message
news:413301c3e42f$29ac0100$a301280a@.phx.gbl...
> I am not a DBA and may have a problem. I am running an
> app that sits on top of the sql desktop engine. I am
> using AD integrated security. My problem is that one of
> the domain admins decided to reformat and reinstall both
> our AD servers.(#$%#) There is a new domain, but there is
> no longer an AD server for the account that "owns" the
> sql database.
> I am still logged in to the server with the account that
> owns the database. I have not logged out since the AD was
> deleted for fear that my database will no longer be
> accessible. As far as I can see, the admin tools
> available to me for the desktop engine don't have the
> ability to change the owner of the database.
> What must I do to ensure that I can access this database?
>
app that sits on top of the sql desktop engine. I am
using AD integrated security. My problem is that one of
the domain admins decided to reformat and reinstall both
our AD servers.(#$%#) There is a new domain, but there is
no longer an AD server for the account that "owns" the
sql database.
I am still logged in to the server with the account that
owns the database. I have not logged out since the AD was
deleted for fear that my database will no longer be
accessible. As far as I can see, the admin tools
available to me for the desktop engine don't have the
ability to change the owner of the database.
What must I do to ensure that I can access this database?You can change the database owner with sp_changedbowner. Run this using the
command-line OSQL utility like the example below:
OSQL -Q "EXEC sp_changedbowner 'sa'" -d MyDatabase -E -S MyServer
By default, members of the local Administrators have sysadmin access to SQL
Server via the 'BULTIN\Administrators' login. This will provide sysadmin
access to your SQL Server instance as long as you can access the machine
with Windows account that is a member of the local Administrators group.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"hhtpnoc" <anonymous@.discussions.microsoft.com> wrote in message
news:413301c3e42f$29ac0100$a301280a@.phx.gbl...
> I am not a DBA and may have a problem. I am running an
> app that sits on top of the sql desktop engine. I am
> using AD integrated security. My problem is that one of
> the domain admins decided to reformat and reinstall both
> our AD servers.(#$%#) There is a new domain, but there is
> no longer an AD server for the account that "owns" the
> sql database.
> I am still logged in to the server with the account that
> owns the database. I have not logged out since the AD was
> deleted for fear that my database will no longer be
> accessible. As far as I can see, the admin tools
> available to me for the desktop engine don't have the
> ability to change the owner of the database.
> What must I do to ensure that I can access this database?
>
deleted AD
I am not a DBA and may have a problem. I am running an
app that sits on top of the sql desktop engine. I am
using AD integrated security. My problem is that one of
the domain admins decided to reformat and reinstall both
our AD servers.(#$%#) There is a new domain, but there is
no longer an AD server for the account that "owns" the
sql database.
I am still logged in to the server with the account that
owns the database. I have not logged out since the AD was
deleted for fear that my database will no longer be
accessible. As far as I can see, the admin tools
available to me for the desktop engine don't have the
ability to change the owner of the database.
What must I do to ensure that I can access this database?You can change the database owner with sp_changedbowner. Run this using the
command-line OSQL utility like the example below:
OSQL -Q "EXEC sp_changedbowner 'sa'" -d MyDatabase -E -S MyServer
By default, members of the local Administrators have sysadmin access to SQL
Server via the 'BULTIN\Administrators' login. This will provide sysadmin
access to your SQL Server instance as long as you can access the machine
with Windows account that is a member of the local Administrators group.
Hope this helps.
Dan Guzman
SQL Server MVP
"hhtpnoc" <anonymous@.discussions.microsoft.com> wrote in message
news:413301c3e42f$29ac0100$a301280a@.phx.gbl...
app that sits on top of the sql desktop engine. I am
using AD integrated security. My problem is that one of
the domain admins decided to reformat and reinstall both
our AD servers.(#$%#) There is a new domain, but there is
no longer an AD server for the account that "owns" the
sql database.
I am still logged in to the server with the account that
owns the database. I have not logged out since the AD was
deleted for fear that my database will no longer be
accessible. As far as I can see, the admin tools
available to me for the desktop engine don't have the
ability to change the owner of the database.
What must I do to ensure that I can access this database?You can change the database owner with sp_changedbowner. Run this using the
command-line OSQL utility like the example below:
OSQL -Q "EXEC sp_changedbowner 'sa'" -d MyDatabase -E -S MyServer
By default, members of the local Administrators have sysadmin access to SQL
Server via the 'BULTIN\Administrators' login. This will provide sysadmin
access to your SQL Server instance as long as you can access the machine
with Windows account that is a member of the local Administrators group.
Hope this helps.
Dan Guzman
SQL Server MVP
"hhtpnoc" <anonymous@.discussions.microsoft.com> wrote in message
news:413301c3e42f$29ac0100$a301280a@.phx.gbl...
quote:
> I am not a DBA and may have a problem. I am running an
> app that sits on top of the sql desktop engine. I am
> using AD integrated security. My problem is that one of
> the domain admins decided to reformat and reinstall both
> our AD servers.(#$%#) There is a new domain, but there is
> no longer an AD server for the account that "owns" the
> sql database.
> I am still logged in to the server with the account that
> owns the database. I have not logged out since the AD was
> deleted for fear that my database will no longer be
> accessible. As far as I can see, the admin tools
> available to me for the desktop engine don't have the
> ability to change the owner of the database.
> What must I do to ensure that I can access this database?
>
Delete user
SQL 2005. and SQL Management studio I have a user 'myuser' in a SQL DB
'mydatabase' under security users. When I try to delete him, I get error
says DB principal owns schema and cant be dropped. I try to remove his role
as DBOwner and it says login name must be specified. (The window above has
his username shown but the loginname field is blank and greyed out/
disabled. I added him to the overall sql DB users / security and it allowed
me to. When I tried to map him to the 'mydatabase' it says 'myuser' already
exists. How can I get rid of this user in the 'mydatabase' DB. I have other
users in the DB that I can delete.
Thanks
bucThe key seems to be that the user owns a schema. See what schema the user ow
ns (schema folder) and
either drop the schema (if empty) or change the owner of the schema to someb
ody else.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<Buc> wrote in message news:OpjsV6ceGHA.1456@.TK2MSFTNGP04.phx.gbl...
> SQL 2005. and SQL Management studio I have a user 'myuser' in a SQL DB 'my
database' under security
> users. When I try to delete him, I get error says DB principal owns schema
and cant be dropped. I
> try to remove his role as DBOwner and it says login name must be specified
. (The window above has
> his username shown but the loginname field is blank and greyed out/ disabl
ed. I added him to the
> overall sql DB users / security and it allowed me to. When I tried to map
him to the 'mydatabase'
> it says 'myuser' already exists. How can I get rid of this user in the 'my
database' DB. I have
> other users in the DB that I can delete.
> Thanks
> buc
>|||Make sure there are no objects owned by this user. If there are any, you
should change the owner and then you should be able to delete this user from
the database.
Anith|||That worked, he had a entry under the schema folder which had zero objects.
I deleted his entry and it worked. Thanks
"Anith Sen" <anith@.bizdatasolutions.com> wrote in message
news:e52E89ceGHA.1276@.TK2MSFTNGP03.phx.gbl...
> Make sure there are no objects owned by this user. If there are any, you
> should change the owner and then you should be able to delete this user
> from the database.
> --
> Anith
>
'mydatabase' under security users. When I try to delete him, I get error
says DB principal owns schema and cant be dropped. I try to remove his role
as DBOwner and it says login name must be specified. (The window above has
his username shown but the loginname field is blank and greyed out/
disabled. I added him to the overall sql DB users / security and it allowed
me to. When I tried to map him to the 'mydatabase' it says 'myuser' already
exists. How can I get rid of this user in the 'mydatabase' DB. I have other
users in the DB that I can delete.
Thanks
bucThe key seems to be that the user owns a schema. See what schema the user ow
ns (schema folder) and
either drop the schema (if empty) or change the owner of the schema to someb
ody else.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<Buc> wrote in message news:OpjsV6ceGHA.1456@.TK2MSFTNGP04.phx.gbl...
> SQL 2005. and SQL Management studio I have a user 'myuser' in a SQL DB 'my
database' under security
> users. When I try to delete him, I get error says DB principal owns schema
and cant be dropped. I
> try to remove his role as DBOwner and it says login name must be specified
. (The window above has
> his username shown but the loginname field is blank and greyed out/ disabl
ed. I added him to the
> overall sql DB users / security and it allowed me to. When I tried to map
him to the 'mydatabase'
> it says 'myuser' already exists. How can I get rid of this user in the 'my
database' DB. I have
> other users in the DB that I can delete.
> Thanks
> buc
>|||Make sure there are no objects owned by this user. If there are any, you
should change the owner and then you should be able to delete this user from
the database.
Anith|||That worked, he had a entry under the schema folder which had zero objects.
I deleted his entry and it worked. Thanks
"Anith Sen" <anith@.bizdatasolutions.com> wrote in message
news:e52E89ceGHA.1276@.TK2MSFTNGP03.phx.gbl...
> Make sure there are no objects owned by this user. If there are any, you
> should change the owner and then you should be able to delete this user
> from the database.
> --
> Anith
>
Subscribe to:
Posts (Atom)