Hello,
I have a SQL server though a hosting company and I am trying to send autoemails using xp_sendmail. The permissions were set and I used the following command to test it.
EXEC master.dbo.xp_sendmail
@.recipients='tracey@.yahoo.com',@.subject='test',@.me ssage='testing
sql stored procedure'
It gave me a message saying "Mail sent" but there none in my e-mail box.
How do I set yp the SQL Mail server, right? Please help. I don't know what is happening.
Thanks,
TraceyHave you checked whether the Mail Service has been turned on and the machine has MS Outlook installed(And it has to work)?|||And an Outlook need to have mail configured using the same account the SQL Server Agent runs as.|||Insead of all that, you could use CDO to send mail, which eliminates the need to have Outlook installed.
Check out this:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cdo/html/_denali_cdo_for_nts_library.asp
and this:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cdo/html/_denali_session_object_cdonts_library_.asp
Showing posts with label permissions. Show all posts
Showing posts with label permissions. Show all posts
Tuesday, March 27, 2012
Sunday, March 25, 2012
authorization and permissions
Hi All,
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
Thanks
First of all, abstraction is the easiest to manage and administrate. In all
regards, use Windows Authentication whenever possible. If this is public
facing, in all likelihood, you will not have Windows Domain Accounts
available for use.
In this case, and in cases where the applicaiton needs to control the
security of the users (that is, keep explicit user identification and
permissions within the application database), it would be better to use a
single Windows Authenticated account to manipulate database calls.
Also, you should not have the Web Services directly manipulate the database.
In stead, you should have application layer services resident on another
server from you Web Server and have the web call these services. The
application tier should then use this single application, Windows
Authenticated account control the connections and calls to the Data Services
tier.
The interfaces exposed from the DBMS should all be done through stored
procedures and ad-hoc requests for reporting and administrative services
should be exposed through Views. No direct base table access should be
granted outside of the development/application support staff, and even then,
restricted to DML activities alone. The DBA should be the only user
authorized to make system level changes, including DDL, and only through a
formalized Change Control process.
Sincerely,
Anthony Thomas
"ReTF" <re.tf@.newsgroup.nospam> wrote in message
news:O3KN$thaFHA.3048@.TK2MSFTNGP12.phx.gbl...
Hi All,
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
Thanks
|||The most secure option is to force all users to have their own login and
make them all trusted logins. Of course, there are typically practical
problems with that approach from web apps as the user that hits the web
server needs to be authenticated against AD for the trusted SQL login
from the web server to work properly and for externally accessible web
apps authenticating the users against AD is often not possible. But
purely from a SQL perspective trusted logins are the most secure method
of connecting.
Storing passwords in your DB is never a good idea if solid security is
what you're aiming for. Storing localised application permissions in
some user table in your DB is fine as long as you have the table locked
down so if a user hacks in somehow they can't "tweak" the permissions
table to change their level of permissions within the app. As far as
SQL permissions go, each different "role" within your app (eg. clerk,
manager, administrator, etc.) should have a corresponding role within
the DB (see sp_addrole and sp_addrolemember in BOL) with the necessary
SQL permissions assigned to the DB roles.
It's best not to use the 'sa' login for anything. In fact, if you have
Windows Authentication only then you cannot login with 'sa' because it's
a SQL login (not a trusted login).
HTH
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
ReTF wrote:
>Hi All,
>
>I'm development a system, and I have doubts about login (authorization and
>permissions)
>This system need be very secure.
>
>The systems have clients that connect in a web service and this web service
>connects in SQL Server.
>
>My doubt is:
>
>What is the best:
>
>Logins here is: Name and password(hash) and what each user can do.
>
>Store logins in one table in my database and always WebServise use SA
>account to manipulate data base?
>
>Use SQL logins for each users?
>
>Use Windows logins for each users?
>
>Thanks
>
>
sql
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
Thanks
First of all, abstraction is the easiest to manage and administrate. In all
regards, use Windows Authentication whenever possible. If this is public
facing, in all likelihood, you will not have Windows Domain Accounts
available for use.
In this case, and in cases where the applicaiton needs to control the
security of the users (that is, keep explicit user identification and
permissions within the application database), it would be better to use a
single Windows Authenticated account to manipulate database calls.
Also, you should not have the Web Services directly manipulate the database.
In stead, you should have application layer services resident on another
server from you Web Server and have the web call these services. The
application tier should then use this single application, Windows
Authenticated account control the connections and calls to the Data Services
tier.
The interfaces exposed from the DBMS should all be done through stored
procedures and ad-hoc requests for reporting and administrative services
should be exposed through Views. No direct base table access should be
granted outside of the development/application support staff, and even then,
restricted to DML activities alone. The DBA should be the only user
authorized to make system level changes, including DDL, and only through a
formalized Change Control process.
Sincerely,
Anthony Thomas
"ReTF" <re.tf@.newsgroup.nospam> wrote in message
news:O3KN$thaFHA.3048@.TK2MSFTNGP12.phx.gbl...
Hi All,
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
Thanks
|||The most secure option is to force all users to have their own login and
make them all trusted logins. Of course, there are typically practical
problems with that approach from web apps as the user that hits the web
server needs to be authenticated against AD for the trusted SQL login
from the web server to work properly and for externally accessible web
apps authenticating the users against AD is often not possible. But
purely from a SQL perspective trusted logins are the most secure method
of connecting.
Storing passwords in your DB is never a good idea if solid security is
what you're aiming for. Storing localised application permissions in
some user table in your DB is fine as long as you have the table locked
down so if a user hacks in somehow they can't "tweak" the permissions
table to change their level of permissions within the app. As far as
SQL permissions go, each different "role" within your app (eg. clerk,
manager, administrator, etc.) should have a corresponding role within
the DB (see sp_addrole and sp_addrolemember in BOL) with the necessary
SQL permissions assigned to the DB roles.
It's best not to use the 'sa' login for anything. In fact, if you have
Windows Authentication only then you cannot login with 'sa' because it's
a SQL login (not a trusted login).
HTH
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
ReTF wrote:
>Hi All,
>
>I'm development a system, and I have doubts about login (authorization and
>permissions)
>This system need be very secure.
>
>The systems have clients that connect in a web service and this web service
>connects in SQL Server.
>
>My doubt is:
>
>What is the best:
>
>Logins here is: Name and password(hash) and what each user can do.
>
>Store logins in one table in my database and always WebServise use SA
>account to manipulate data base?
>
>Use SQL logins for each users?
>
>Use Windows logins for each users?
>
>Thanks
>
>
sql
authorization and permissions
Hi All,
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
ThanksFirst of all, abstraction is the easiest to manage and administrate. In all
regards, use Windows Authentication whenever possible. If this is public
facing, in all likelihood, you will not have Windows Domain Accounts
available for use.
In this case, and in cases where the applicaiton needs to control the
security of the users (that is, keep explicit user identification and
permissions within the application database), it would be better to use a
single Windows Authenticated account to manipulate database calls.
Also, you should not have the Web Services directly manipulate the database.
In stead, you should have application layer services resident on another
server from you Web Server and have the web call these services. The
application tier should then use this single application, Windows
Authenticated account control the connections and calls to the Data Services
tier.
The interfaces exposed from the DBMS should all be done through stored
procedures and ad-hoc requests for reporting and administrative services
should be exposed through Views. No direct base table access should be
granted outside of the development/application support staff, and even then,
restricted to DML activities alone. The DBA should be the only user
authorized to make system level changes, including DDL, and only through a
formalized Change Control process.
Sincerely,
Anthony Thomas
"ReTF" <re.tf@.newsgroup.nospam> wrote in message
news:O3KN$thaFHA.3048@.TK2MSFTNGP12.phx.gbl...
Hi All,
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
Thanks|||This is a multi-part message in MIME format.
--090003030806010808040200
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
The most secure option is to force all users to have their own login and
make them all trusted logins. Of course, there are typically practical
problems with that approach from web apps as the user that hits the web
server needs to be authenticated against AD for the trusted SQL login
from the web server to work properly and for externally accessible web
apps authenticating the users against AD is often not possible. But
purely from a SQL perspective trusted logins are the most secure method
of connecting.
Storing passwords in your DB is never a good idea if solid security is
what you're aiming for. Storing localised application permissions in
some user table in your DB is fine as long as you have the table locked
down so if a user hacks in somehow they can't "tweak" the permissions
table to change their level of permissions within the app. As far as
SQL permissions go, each different "role" within your app (eg. clerk,
manager, administrator, etc.) should have a corresponding role within
the DB (see sp_addrole and sp_addrolemember in BOL) with the necessary
SQL permissions assigned to the DB roles.
It's best not to use the 'sa' login for anything. In fact, if you have
Windows Authentication only then you cannot login with 'sa' because it's
a SQL login (not a trusted login).
HTH
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
ReTF wrote:
>Hi All,
>
>I'm development a system, and I have doubts about login (authorization and
>permissions)
>This system need be very secure.
>
>The systems have clients that connect in a web service and this web service
>connects in SQL Server.
>
>My doubt is:
>
>What is the best:
>
>Logins here is: Name and password(hash) and what each user can do.
>
>Store logins in one table in my database and always WebServise use SA
>account to manipulate data base?
>
>Use SQL logins for each users?
>
>Use Windows logins for each users?
>
>Thanks
>
>
--090003030806010808040200
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>The most secure option is to force all users to have their own
login and make them all trusted logins. Of course, there are typically
practical problems with that approach from web apps as the user that
hits the web server needs to be authenticated against AD for the
trusted SQL login from the web server to work properly and for
externally accessible web apps authenticating the users against AD is
often not possible. But purely from a SQL perspective trusted logins
are the most secure method of connecting.<br>
<br>
Storing passwords in your DB is never a good idea if solid security is
what you're aiming for. Storing localised application permissions in
some user table in your DB is fine as long as you have the table locked
down so if a user hacks in somehow they can't "tweak" the permissions
table to change their level of permissions within the app. As far as
SQL permissions go, each different "role" within your app (eg. clerk,
manager, administrator, etc.) should have a corresponding role within
the DB (see sp_addrole and sp_addrolemember in BOL) with the necessary
SQL permissions assigned to the DB roles.<br>
<br>
It's best not to use the 'sa' login for anything. In fact, if you have
Windows Authentication only then you cannot login with 'sa' because
it's a SQL login (not a trusted login).<br>
<br>
HTH<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
ReTF wrote:
<blockquote cite="midO3KN$thaFHA.3048@.TK2MSFTNGP12.phx.gbl" type="cite">
<pre wrap="">Hi All,
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
Thanks
</pre>
</blockquote>
</body>
</html>
--090003030806010808040200--
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
ThanksFirst of all, abstraction is the easiest to manage and administrate. In all
regards, use Windows Authentication whenever possible. If this is public
facing, in all likelihood, you will not have Windows Domain Accounts
available for use.
In this case, and in cases where the applicaiton needs to control the
security of the users (that is, keep explicit user identification and
permissions within the application database), it would be better to use a
single Windows Authenticated account to manipulate database calls.
Also, you should not have the Web Services directly manipulate the database.
In stead, you should have application layer services resident on another
server from you Web Server and have the web call these services. The
application tier should then use this single application, Windows
Authenticated account control the connections and calls to the Data Services
tier.
The interfaces exposed from the DBMS should all be done through stored
procedures and ad-hoc requests for reporting and administrative services
should be exposed through Views. No direct base table access should be
granted outside of the development/application support staff, and even then,
restricted to DML activities alone. The DBA should be the only user
authorized to make system level changes, including DDL, and only through a
formalized Change Control process.
Sincerely,
Anthony Thomas
"ReTF" <re.tf@.newsgroup.nospam> wrote in message
news:O3KN$thaFHA.3048@.TK2MSFTNGP12.phx.gbl...
Hi All,
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
Thanks|||This is a multi-part message in MIME format.
--090003030806010808040200
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
The most secure option is to force all users to have their own login and
make them all trusted logins. Of course, there are typically practical
problems with that approach from web apps as the user that hits the web
server needs to be authenticated against AD for the trusted SQL login
from the web server to work properly and for externally accessible web
apps authenticating the users against AD is often not possible. But
purely from a SQL perspective trusted logins are the most secure method
of connecting.
Storing passwords in your DB is never a good idea if solid security is
what you're aiming for. Storing localised application permissions in
some user table in your DB is fine as long as you have the table locked
down so if a user hacks in somehow they can't "tweak" the permissions
table to change their level of permissions within the app. As far as
SQL permissions go, each different "role" within your app (eg. clerk,
manager, administrator, etc.) should have a corresponding role within
the DB (see sp_addrole and sp_addrolemember in BOL) with the necessary
SQL permissions assigned to the DB roles.
It's best not to use the 'sa' login for anything. In fact, if you have
Windows Authentication only then you cannot login with 'sa' because it's
a SQL login (not a trusted login).
HTH
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
ReTF wrote:
>Hi All,
>
>I'm development a system, and I have doubts about login (authorization and
>permissions)
>This system need be very secure.
>
>The systems have clients that connect in a web service and this web service
>connects in SQL Server.
>
>My doubt is:
>
>What is the best:
>
>Logins here is: Name and password(hash) and what each user can do.
>
>Store logins in one table in my database and always WebServise use SA
>account to manipulate data base?
>
>Use SQL logins for each users?
>
>Use Windows logins for each users?
>
>Thanks
>
>
--090003030806010808040200
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>The most secure option is to force all users to have their own
login and make them all trusted logins. Of course, there are typically
practical problems with that approach from web apps as the user that
hits the web server needs to be authenticated against AD for the
trusted SQL login from the web server to work properly and for
externally accessible web apps authenticating the users against AD is
often not possible. But purely from a SQL perspective trusted logins
are the most secure method of connecting.<br>
<br>
Storing passwords in your DB is never a good idea if solid security is
what you're aiming for. Storing localised application permissions in
some user table in your DB is fine as long as you have the table locked
down so if a user hacks in somehow they can't "tweak" the permissions
table to change their level of permissions within the app. As far as
SQL permissions go, each different "role" within your app (eg. clerk,
manager, administrator, etc.) should have a corresponding role within
the DB (see sp_addrole and sp_addrolemember in BOL) with the necessary
SQL permissions assigned to the DB roles.<br>
<br>
It's best not to use the 'sa' login for anything. In fact, if you have
Windows Authentication only then you cannot login with 'sa' because
it's a SQL login (not a trusted login).<br>
<br>
HTH<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
ReTF wrote:
<blockquote cite="midO3KN$thaFHA.3048@.TK2MSFTNGP12.phx.gbl" type="cite">
<pre wrap="">Hi All,
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
Thanks
</pre>
</blockquote>
</body>
</html>
--090003030806010808040200--
authorization and permissions
Hi All,
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
ThanksFirst of all, abstraction is the easiest to manage and administrate. In all
regards, use Windows Authentication whenever possible. If this is public
facing, in all likelihood, you will not have Windows Domain Accounts
available for use.
In this case, and in cases where the applicaiton needs to control the
security of the users (that is, keep explicit user identification and
permissions within the application database), it would be better to use a
single Windows Authenticated account to manipulate database calls.
Also, you should not have the Web Services directly manipulate the database.
In stead, you should have application layer services resident on another
server from you Web Server and have the web call these services. The
application tier should then use this single application, Windows
Authenticated account control the connections and calls to the Data Services
tier.
The interfaces exposed from the DBMS should all be done through stored
procedures and ad-hoc requests for reporting and administrative services
should be exposed through Views. No direct base table access should be
granted outside of the development/application support staff, and even then,
restricted to DML activities alone. The DBA should be the only user
authorized to make system level changes, including DDL, and only through a
formalized Change Control process.
Sincerely,
Anthony Thomas
"ReTF" <re.tf@.newsgroup.nospam> wrote in message
news:O3KN$thaFHA.3048@.TK2MSFTNGP12.phx.gbl...
Hi All,
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
Thanks|||The most secure option is to force all users to have their own login and
make them all trusted logins. Of course, there are typically practical
problems with that approach from web apps as the user that hits the web
server needs to be authenticated against AD for the trusted SQL login
from the web server to work properly and for externally accessible web
apps authenticating the users against AD is often not possible. But
purely from a SQL perspective trusted logins are the most secure method
of connecting.
Storing passwords in your DB is never a good idea if solid security is
what you're aiming for. Storing localised application permissions in
some user table in your DB is fine as long as you have the table locked
down so if a user hacks in somehow they can't "tweak" the permissions
table to change their level of permissions within the app. As far as
SQL permissions go, each different "role" within your app (eg. clerk,
manager, administrator, etc.) should have a corresponding role within
the DB (see sp_addrole and sp_addrolemember in BOL) with the necessary
SQL permissions assigned to the DB roles.
It's best not to use the 'sa' login for anything. In fact, if you have
Windows Authentication only then you cannot login with 'sa' because it's
a SQL login (not a trusted login).
HTH
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
ReTF wrote:
>Hi All,
>
>I'm development a system, and I have doubts about login (authorization and
>permissions)
>This system need be very secure.
>
>The systems have clients that connect in a web service and this web service
>connects in SQL Server.
>
>My doubt is:
>
>What is the best:
>
>Logins here is: Name and password(hash) and what each user can do.
>
>Store logins in one table in my database and always WebServise use SA
>account to manipulate data base?
>
>Use SQL logins for each users?
>
>Use Windows logins for each users?
>
>Thanks
>
>
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
ThanksFirst of all, abstraction is the easiest to manage and administrate. In all
regards, use Windows Authentication whenever possible. If this is public
facing, in all likelihood, you will not have Windows Domain Accounts
available for use.
In this case, and in cases where the applicaiton needs to control the
security of the users (that is, keep explicit user identification and
permissions within the application database), it would be better to use a
single Windows Authenticated account to manipulate database calls.
Also, you should not have the Web Services directly manipulate the database.
In stead, you should have application layer services resident on another
server from you Web Server and have the web call these services. The
application tier should then use this single application, Windows
Authenticated account control the connections and calls to the Data Services
tier.
The interfaces exposed from the DBMS should all be done through stored
procedures and ad-hoc requests for reporting and administrative services
should be exposed through Views. No direct base table access should be
granted outside of the development/application support staff, and even then,
restricted to DML activities alone. The DBA should be the only user
authorized to make system level changes, including DDL, and only through a
formalized Change Control process.
Sincerely,
Anthony Thomas
"ReTF" <re.tf@.newsgroup.nospam> wrote in message
news:O3KN$thaFHA.3048@.TK2MSFTNGP12.phx.gbl...
Hi All,
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
Thanks|||The most secure option is to force all users to have their own login and
make them all trusted logins. Of course, there are typically practical
problems with that approach from web apps as the user that hits the web
server needs to be authenticated against AD for the trusted SQL login
from the web server to work properly and for externally accessible web
apps authenticating the users against AD is often not possible. But
purely from a SQL perspective trusted logins are the most secure method
of connecting.
Storing passwords in your DB is never a good idea if solid security is
what you're aiming for. Storing localised application permissions in
some user table in your DB is fine as long as you have the table locked
down so if a user hacks in somehow they can't "tweak" the permissions
table to change their level of permissions within the app. As far as
SQL permissions go, each different "role" within your app (eg. clerk,
manager, administrator, etc.) should have a corresponding role within
the DB (see sp_addrole and sp_addrolemember in BOL) with the necessary
SQL permissions assigned to the DB roles.
It's best not to use the 'sa' login for anything. In fact, if you have
Windows Authentication only then you cannot login with 'sa' because it's
a SQL login (not a trusted login).
HTH
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
ReTF wrote:
>Hi All,
>
>I'm development a system, and I have doubts about login (authorization and
>permissions)
>This system need be very secure.
>
>The systems have clients that connect in a web service and this web service
>connects in SQL Server.
>
>My doubt is:
>
>What is the best:
>
>Logins here is: Name and password(hash) and what each user can do.
>
>Store logins in one table in my database and always WebServise use SA
>account to manipulate data base?
>
>Use SQL logins for each users?
>
>Use Windows logins for each users?
>
>Thanks
>
>
authorization and permissions
Hi All,
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
ThanksHello,
I notice you have posted the same question in our SQLServer newsgroup,
which have been responded. So please check the answers there.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm development a system, and I have doubts about login (authorization and
permissions)
This system need be very secure.
The systems have clients that connect in a web service and this web service
connects in SQL Server.
My doubt is:
What is the best:
Logins here is: Name and password(hash) and what each user can do.
Store logins in one table in my database and always WebServise use SA
account to manipulate data base?
Use SQL logins for each users?
Use Windows logins for each users?
ThanksHello,
I notice you have posted the same question in our SQLServer newsgroup,
which have been responded. So please check the answers there.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Thursday, March 22, 2012
Authentication permissions
I'm fairly certain that I understand the difference between the AUTHENTICATE SERVER and AUTHENTICATE permission, but I'm not positive.
For these purposes, I'm leaving off the authorization portion as well as assuming a TSQL endpoint.
My understanding:
The authentication process is broken into two stages - connection and authentication. In order to successfully authenticate to an instance, the following must apply:
1. I must have CONNECT SQL permission
2. I must have CONNECT permission on the endpoint that I am using
3. The endpoint that I am using must be in a STARTED state
4. The login that I am using must be enabled
Once the connection is established, I need AUTHENTICATE SERVER permission in order to authenticate to the instance. (Or do I simply need AUTHENTICATE permission?)
AUTHENTICATE & AUTHENTICATE SERVER permissions are only used when using EXECUTE AS in cross database and server-access (respectively) scenarios.
When a new session is established in SQL Server, the server itself will perform the authentication and the no AUTHENTICATEAUTHENTICATE SERVER permission is checked.
When using EXECUTE AS USER, permissions are checked at the DB scope, therefore the DBO has absolute control over this type of impersonation, and the DBO is said to vouch for the token and becomes the authenticator. In case of a digitally signed module (marked with EXECUTE AS) the story is similar, but the certificate can act as an authenticator.
In order to avoid unintended escalations, by default these impersonated tokens cannot move outside the current database (i.e. cannot access resources outside it) unless the DB is marked as trustworthy or they come from a digitally signed module. Being able to get outside the DB is not sufficient, the authenticator must be trusted at the scope of the resource the impersonated context is trying to access; for example, if trying to access a table on another DB, the DBO of the target DB must have granted AUTHENTICATE to the authenticator of the impersonated context.
I strongly recommend reading the following topic from BOL: Extending Database Impersonation by Using EXECUTE AS (http://msdn2.microsoft.com/en-us/library/ms188304.aspx )
I hope this information helps,
-Raul Garcia
SDE/T
SQL Server Engine
sqlAuthentication permissions
Hi,
How do I change RSs authentication from Windows to SQL Server only? What
config files need to be changed?
What else needs to be changed? I just want authentication at the SQL Server
level only.
If I can't how about using Forms authentication instead for RS. What do I
need to change for this to happen?
Thanks,
JJ> How do I change RSs authentication from Windows to SQL Server only?
Can you explain what you mean here?...[If you mean the credentials RS needs
to connect to the SQL server and execute the report you can set SQL Srv up
to use SQL Server authentication, set up a user(s) that has access to your
database, and in the shared data source choose the 'Connect Using' option
you want.]
> If I can't how about using Forms authentication instead for RS. What do I
> need to change for this to happen?
Here's a white paper that can get you started:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
Adrian M.
MCP
"JJ" <jjmraz@.-NOspAM*hotmail.com> wrote in message
news:%23s$77MIBFHA.2112@.TK2MSFTNGP09.phx.gbl...
> Hi,
> How do I change RSs authentication from Windows to SQL Server only? What
> config files need to be changed?
> What else needs to be changed? I just want authentication at the SQL
> Server
> level only.
>
> Thanks,
> JJ
>|||Adrian,
What Connect Using option is appropriate when the SQL Server user name and
password are specified in the connection string?
That is, using SQL Authentication to connect from RS to the datasource. I
want an option that says SQL Authentication in addition to all the windows
authentication options already there.
Seems a lot of people are confused about this. My user, report services and
data source SQL server are on three different computers, and I don't have
kerberos installed.
Thanks
Martin
"Adrian M." <absolutelynospam@.nodomain_.com> wrote in message
news:OoSThJKBFHA.2112@.TK2MSFTNGP14.phx.gbl...
>> How do I change RSs authentication from Windows to SQL Server only?
> Can you explain what you mean here?...[If you mean the credentials RS
> needs to connect to the SQL server and execute the report you can set SQL
> Srv up to use SQL Server authentication, set up a user(s) that has access
> to your database, and in the shared data source choose the 'Connect Using'
> option you want.]
>> If I can't how about using Forms authentication instead for RS. What do I
>> need to change for this to happen?
> Here's a white paper that can get you started:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
>
> --
> Adrian M.
> MCP
>|||Looks like No Credentials is the appropriate option when passing sql auth
credentials in connection string.
Martin
"Martin" <x@.y.z> wrote in message
news:efIbvyWIFHA.3108@.tk2msftngp13.phx.gbl...
> Adrian,
> What Connect Using option is appropriate when the SQL Server user name and
> password are specified in the connection string?
> That is, using SQL Authentication to connect from RS to the datasource. I
> want an option that says SQL Authentication in addition to all the windows
> authentication options already there.
> Seems a lot of people are confused about this. My user, report services
> and data source SQL server are on three different computers, and I don't
> have kerberos installed.
> Thanks
> Martin
> "Adrian M." <absolutelynospam@.nodomain_.com> wrote in message
> news:OoSThJKBFHA.2112@.TK2MSFTNGP14.phx.gbl...
>> How do I change RSs authentication from Windows to SQL Server only?
>> Can you explain what you mean here?...[If you mean the credentials RS
>> needs to connect to the SQL server and execute the report you can set SQL
>> Srv up to use SQL Server authentication, set up a user(s) that has access
>> to your database, and in the shared data source choose the 'Connect
>> Using' option you want.]
>> If I can't how about using Forms authentication instead for RS. What do
>> I
>> need to change for this to happen?
>> Here's a white paper that can get you started:
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
>>
>> --
>> Adrian M.
>> MCP
>|||I actually don't pass the SQL auth credentials in the connect string. I use
the 'Credentials Stored Securely in the Report Server' option. That's
because most of my reports have schedule subscriptions. I haven't had an
issue with this setup.
--
Adrian M.
MCP
"Martin" <x@.y.z> wrote in message
news:uLbKntXIFHA.2456@.TK2MSFTNGP09.phx.gbl...
> Looks like No Credentials is the appropriate option when passing sql auth
> credentials in connection string.
> Martin
> "Martin" <x@.y.z> wrote in message
> news:efIbvyWIFHA.3108@.tk2msftngp13.phx.gbl...
>> Adrian,
>> What Connect Using option is appropriate when the SQL Server user name
>> and password are specified in the connection string?
>> That is, using SQL Authentication to connect from RS to the datasource.
>> I want an option that says SQL Authentication in addition to all the
>> windows authentication options already there.
>> Seems a lot of people are confused about this. My user, report services
>> and data source SQL server are on three different computers, and I don't
>> have kerberos installed.
>> Thanks
>> Martin
>> "Adrian M." <absolutelynospam@.nodomain_.com> wrote in message
>> news:OoSThJKBFHA.2112@.TK2MSFTNGP14.phx.gbl...
>> How do I change RSs authentication from Windows to SQL Server only?
>> Can you explain what you mean here?...[If you mean the credentials RS
>> needs to connect to the SQL server and execute the report you can set
>> SQL Srv up to use SQL Server authentication, set up a user(s) that has
>> access to your database, and in the shared data source choose the
>> 'Connect Using' option you want.]
>> If I can't how about using Forms authentication instead for RS. What do
>> I
>> need to change for this to happen?
>> Here's a white paper that can get you started:
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
>>
>> --
>> Adrian M.
>> MCP
>>
>
How do I change RSs authentication from Windows to SQL Server only? What
config files need to be changed?
What else needs to be changed? I just want authentication at the SQL Server
level only.
If I can't how about using Forms authentication instead for RS. What do I
need to change for this to happen?
Thanks,
JJ> How do I change RSs authentication from Windows to SQL Server only?
Can you explain what you mean here?...[If you mean the credentials RS needs
to connect to the SQL server and execute the report you can set SQL Srv up
to use SQL Server authentication, set up a user(s) that has access to your
database, and in the shared data source choose the 'Connect Using' option
you want.]
> If I can't how about using Forms authentication instead for RS. What do I
> need to change for this to happen?
Here's a white paper that can get you started:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
Adrian M.
MCP
"JJ" <jjmraz@.-NOspAM*hotmail.com> wrote in message
news:%23s$77MIBFHA.2112@.TK2MSFTNGP09.phx.gbl...
> Hi,
> How do I change RSs authentication from Windows to SQL Server only? What
> config files need to be changed?
> What else needs to be changed? I just want authentication at the SQL
> Server
> level only.
>
> Thanks,
> JJ
>|||Adrian,
What Connect Using option is appropriate when the SQL Server user name and
password are specified in the connection string?
That is, using SQL Authentication to connect from RS to the datasource. I
want an option that says SQL Authentication in addition to all the windows
authentication options already there.
Seems a lot of people are confused about this. My user, report services and
data source SQL server are on three different computers, and I don't have
kerberos installed.
Thanks
Martin
"Adrian M." <absolutelynospam@.nodomain_.com> wrote in message
news:OoSThJKBFHA.2112@.TK2MSFTNGP14.phx.gbl...
>> How do I change RSs authentication from Windows to SQL Server only?
> Can you explain what you mean here?...[If you mean the credentials RS
> needs to connect to the SQL server and execute the report you can set SQL
> Srv up to use SQL Server authentication, set up a user(s) that has access
> to your database, and in the shared data source choose the 'Connect Using'
> option you want.]
>> If I can't how about using Forms authentication instead for RS. What do I
>> need to change for this to happen?
> Here's a white paper that can get you started:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
>
> --
> Adrian M.
> MCP
>|||Looks like No Credentials is the appropriate option when passing sql auth
credentials in connection string.
Martin
"Martin" <x@.y.z> wrote in message
news:efIbvyWIFHA.3108@.tk2msftngp13.phx.gbl...
> Adrian,
> What Connect Using option is appropriate when the SQL Server user name and
> password are specified in the connection string?
> That is, using SQL Authentication to connect from RS to the datasource. I
> want an option that says SQL Authentication in addition to all the windows
> authentication options already there.
> Seems a lot of people are confused about this. My user, report services
> and data source SQL server are on three different computers, and I don't
> have kerberos installed.
> Thanks
> Martin
> "Adrian M." <absolutelynospam@.nodomain_.com> wrote in message
> news:OoSThJKBFHA.2112@.TK2MSFTNGP14.phx.gbl...
>> How do I change RSs authentication from Windows to SQL Server only?
>> Can you explain what you mean here?...[If you mean the credentials RS
>> needs to connect to the SQL server and execute the report you can set SQL
>> Srv up to use SQL Server authentication, set up a user(s) that has access
>> to your database, and in the shared data source choose the 'Connect
>> Using' option you want.]
>> If I can't how about using Forms authentication instead for RS. What do
>> I
>> need to change for this to happen?
>> Here's a white paper that can get you started:
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
>>
>> --
>> Adrian M.
>> MCP
>|||I actually don't pass the SQL auth credentials in the connect string. I use
the 'Credentials Stored Securely in the Report Server' option. That's
because most of my reports have schedule subscriptions. I haven't had an
issue with this setup.
--
Adrian M.
MCP
"Martin" <x@.y.z> wrote in message
news:uLbKntXIFHA.2456@.TK2MSFTNGP09.phx.gbl...
> Looks like No Credentials is the appropriate option when passing sql auth
> credentials in connection string.
> Martin
> "Martin" <x@.y.z> wrote in message
> news:efIbvyWIFHA.3108@.tk2msftngp13.phx.gbl...
>> Adrian,
>> What Connect Using option is appropriate when the SQL Server user name
>> and password are specified in the connection string?
>> That is, using SQL Authentication to connect from RS to the datasource.
>> I want an option that says SQL Authentication in addition to all the
>> windows authentication options already there.
>> Seems a lot of people are confused about this. My user, report services
>> and data source SQL server are on three different computers, and I don't
>> have kerberos installed.
>> Thanks
>> Martin
>> "Adrian M." <absolutelynospam@.nodomain_.com> wrote in message
>> news:OoSThJKBFHA.2112@.TK2MSFTNGP14.phx.gbl...
>> How do I change RSs authentication from Windows to SQL Server only?
>> Can you explain what you mean here?...[If you mean the credentials RS
>> needs to connect to the SQL server and execute the report you can set
>> SQL Srv up to use SQL Server authentication, set up a user(s) that has
>> access to your database, and in the shared data source choose the
>> 'Connect Using' option you want.]
>> If I can't how about using Forms authentication instead for RS. What do
>> I
>> need to change for this to happen?
>> Here's a white paper that can get you started:
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
>>
>> --
>> Adrian M.
>> MCP
>>
>
Thursday, March 8, 2012
Audit Tools?
I would like to generate a report detailing permissions of users and groups
per database on my server. What would be the best way to go about doing this
? (I dont want to do this through enterprise manager).
A SQL Script to do this would be PERFECT :)
Thanks,
JustinAre you looking for detailed object & statement permissions for each user or
something simple like the one provided by the system procedure sp_helpuser?
Anith|||ME Too! I'm looking for some way to audit which user has access to which DB
and what Database roles they have. The output of SP_helpuser would work, but
I want it to run against all the databases in a server and save the results
so I can make a report. Other people have got to be interested in such a too
l.
Any help would be appreciated..
"Anith Sen" wrote:
> Are you looking for detailed object & statement permissions for each user
or
> something simple like the one provided by the system procedure sp_helpuser
?
> --
> Anith
>
>
per database on my server. What would be the best way to go about doing this
? (I dont want to do this through enterprise manager).
A SQL Script to do this would be PERFECT :)
Thanks,
JustinAre you looking for detailed object & statement permissions for each user or
something simple like the one provided by the system procedure sp_helpuser?
Anith|||ME Too! I'm looking for some way to audit which user has access to which DB
and what Database roles they have. The output of SP_helpuser would work, but
I want it to run against all the databases in a server and save the results
so I can make a report. Other people have got to be interested in such a too
l.
Any help would be appreciated..
"Anith Sen" wrote:
> Are you looking for detailed object & statement permissions for each user
or
> something simple like the one provided by the system procedure sp_helpuser
?
> --
> Anith
>
>
Saturday, February 25, 2012
ATX Caribou, ME
I try to create assembly with UNSAFE permissions.
I granted "unsafe assembly" to my login, set TRUSTWORTHY property ON.
Now I have this error:
Could not obtain information about Windows NT group/user <MyDomain>/<MyName>, error code 0x5. (Microsoft SQL Server, Error: 15404).
How to resolve this?
Looks like your server isn't able to reach the D.C. to get information on your particular user/group...have you verified connectivity to the domain controller?
|||On a side note, it isn't recommended setting the TRUSTWORTHY property to ON if you only need to create an unsafe assembly. You can also create an asymmetric key, map a login to that key, and grant UNSAFE permission to the login to create an unsafe assembly. See http://msdn2.microsoft.com/ms345106(en-US,SQL.90).aspx for more info.|||Chad, how to verify connectivity to D.C.?|||I've gotten that error before. I think the owner of your database doesn't have permission to create assemblies. Try running sp_ChangeDBOwner 'sa' to change the owner of your database to sa.|||
Good Morning,
Is this the same Chad Boyd from Mars Hill who used to work for ATX in Caribou, ME?
ChrisRogeski@.gmail.com
Sunday, February 19, 2012
attempt to copy 2005 db ouside my network shows wrong db?
I connected to an sql 2005 located out on the Internet.
I can export the database I have permissions for and its data ok.
When I right click on the db and choose copy, I get an error at the end of the
wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened because
it is offline. Error 942.
That database shows up in the managment console, and it is offline, but it is
not the one I right clicked on to copy. I don't have permission to put that
database online, just permissions for the one I want to copy.
How can I resolve this?
--
Thanks in advance, Les CaudleHi
I am not sure why this is not selecting your database when you right click!
Have you tried left clicking before you right click?
An althernative you be to backup and restore the database into a new copy,
you can do this in a query window. If you need to do this often then creating
a script will probably end up being quicker.
John
"Les Caudle" wrote:
> I connected to an sql 2005 located out on the Internet.
> I can export the database I have permissions for and its data ok.
> When I right click on the db and choose copy, I get an error at the end of the
> wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened because
> it is offline. Error 942.
> That database shows up in the managment console, and it is offline, but it is
> not the one I right clicked on to copy. I don't have permission to put that
> database online, just permissions for the one I want to copy.
> How can I resolve this?
> --
> Thanks in advance, Les Caudle
>|||John - Yes, I'd clicked on the database first. Very strange.
This is on a client's ISP's shared web server. I only have access to his
database - and am going to need to grab it.
Can I backup and restore in this circumstance - as you suggested? I think I'm
going to be limited in what I can do.
Thanks, Les Caudle
On Sun, 25 Jun 2006 00:00:02 -0700, John Bell <jbellnewsposts@.hotmail.com>
wrote:
>Hi
>I am not sure why this is not selecting your database when you right click!
>Have you tried left clicking before you right click?
>An althernative you be to backup and restore the database into a new copy,
>you can do this in a query window. If you need to do this often then creating
>a script will probably end up being quicker.
>John
>"Les Caudle" wrote:
>> I connected to an sql 2005 located out on the Internet.
>> I can export the database I have permissions for and its data ok.
>> When I right click on the db and choose copy, I get an error at the end of the
>> wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened because
>> it is offline. Error 942.
>> That database shows up in the managment console, and it is offline, but it is
>> not the one I right clicked on to copy. I don't have permission to put that
>> database online, just permissions for the one I want to copy.
>> How can I resolve this?
>> --
>> Thanks in advance, Les Caudle|||Les Caudle wrote:
> John - Yes, I'd clicked on the database first. Very strange.
> This is on a client's ISP's shared web server. I only have access to his
> database - and am going to need to grab it.
> Can I backup and restore in this circumstance - as you suggested? I think I'm
> going to be limited in what I can do.
>
Providing you can connect with Query Analyzer or Management Studio, and
have a directory that SQL can write to, you should be able to use the
BACKUP and RESTORE commands to do a backup and restore.|||Hi
To backup the datbase you will need in the db_backupoperator, db_owner or a
sysadmin role, for restoring you will need to be a sysadmin or in dbcreator
role.
To use sp_attach_db you will need CREATE DATABASE, CREATE ANY DATABASE, or
ALTER ANY DATABASE permission, for sp_detach_db you will need to be a
db_owner.
I suspect that the copy wizard may not be working because you fail on some
or all of these privileges. By doing a manual backup you may get a message
saying that you do not have the privileges to carry out the opertation.
John
"Les Caudle" wrote:
> John - Yes, I'd clicked on the database first. Very strange.
> This is on a client's ISP's shared web server. I only have access to his
> database - and am going to need to grab it.
> Can I backup and restore in this circumstance - as you suggested? I think I'm
> going to be limited in what I can do.
> Thanks, Les Caudle
>
> On Sun, 25 Jun 2006 00:00:02 -0700, John Bell <jbellnewsposts@.hotmail.com>
> wrote:
> >Hi
> >
> >I am not sure why this is not selecting your database when you right click!
> >Have you tried left clicking before you right click?
> >
> >An althernative you be to backup and restore the database into a new copy,
> >you can do this in a query window. If you need to do this often then creating
> >a script will probably end up being quicker.
> >
> >John
> >
> >"Les Caudle" wrote:
> >
> >> I connected to an sql 2005 located out on the Internet.
> >>
> >> I can export the database I have permissions for and its data ok.
> >>
> >> When I right click on the db and choose copy, I get an error at the end of the
> >> wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened because
> >> it is offline. Error 942.
> >>
> >> That database shows up in the managment console, and it is offline, but it is
> >> not the one I right clicked on to copy. I don't have permission to put that
> >> database online, just permissions for the one I want to copy.
> >>
> >> How can I resolve this?
> >> --
> >> Thanks in advance, Les Caudle
> >>
>
I can export the database I have permissions for and its data ok.
When I right click on the db and choose copy, I get an error at the end of the
wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened because
it is offline. Error 942.
That database shows up in the managment console, and it is offline, but it is
not the one I right clicked on to copy. I don't have permission to put that
database online, just permissions for the one I want to copy.
How can I resolve this?
--
Thanks in advance, Les CaudleHi
I am not sure why this is not selecting your database when you right click!
Have you tried left clicking before you right click?
An althernative you be to backup and restore the database into a new copy,
you can do this in a query window. If you need to do this often then creating
a script will probably end up being quicker.
John
"Les Caudle" wrote:
> I connected to an sql 2005 located out on the Internet.
> I can export the database I have permissions for and its data ok.
> When I right click on the db and choose copy, I get an error at the end of the
> wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened because
> it is offline. Error 942.
> That database shows up in the managment console, and it is offline, but it is
> not the one I right clicked on to copy. I don't have permission to put that
> database online, just permissions for the one I want to copy.
> How can I resolve this?
> --
> Thanks in advance, Les Caudle
>|||John - Yes, I'd clicked on the database first. Very strange.
This is on a client's ISP's shared web server. I only have access to his
database - and am going to need to grab it.
Can I backup and restore in this circumstance - as you suggested? I think I'm
going to be limited in what I can do.
Thanks, Les Caudle
On Sun, 25 Jun 2006 00:00:02 -0700, John Bell <jbellnewsposts@.hotmail.com>
wrote:
>Hi
>I am not sure why this is not selecting your database when you right click!
>Have you tried left clicking before you right click?
>An althernative you be to backup and restore the database into a new copy,
>you can do this in a query window. If you need to do this often then creating
>a script will probably end up being quicker.
>John
>"Les Caudle" wrote:
>> I connected to an sql 2005 located out on the Internet.
>> I can export the database I have permissions for and its data ok.
>> When I right click on the db and choose copy, I get an error at the end of the
>> wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened because
>> it is offline. Error 942.
>> That database shows up in the managment console, and it is offline, but it is
>> not the one I right clicked on to copy. I don't have permission to put that
>> database online, just permissions for the one I want to copy.
>> How can I resolve this?
>> --
>> Thanks in advance, Les Caudle|||Les Caudle wrote:
> John - Yes, I'd clicked on the database first. Very strange.
> This is on a client's ISP's shared web server. I only have access to his
> database - and am going to need to grab it.
> Can I backup and restore in this circumstance - as you suggested? I think I'm
> going to be limited in what I can do.
>
Providing you can connect with Query Analyzer or Management Studio, and
have a directory that SQL can write to, you should be able to use the
BACKUP and RESTORE commands to do a backup and restore.|||Hi
To backup the datbase you will need in the db_backupoperator, db_owner or a
sysadmin role, for restoring you will need to be a sysadmin or in dbcreator
role.
To use sp_attach_db you will need CREATE DATABASE, CREATE ANY DATABASE, or
ALTER ANY DATABASE permission, for sp_detach_db you will need to be a
db_owner.
I suspect that the copy wizard may not be working because you fail on some
or all of these privileges. By doing a manual backup you may get a message
saying that you do not have the privileges to carry out the opertation.
John
"Les Caudle" wrote:
> John - Yes, I'd clicked on the database first. Very strange.
> This is on a client's ISP's shared web server. I only have access to his
> database - and am going to need to grab it.
> Can I backup and restore in this circumstance - as you suggested? I think I'm
> going to be limited in what I can do.
> Thanks, Les Caudle
>
> On Sun, 25 Jun 2006 00:00:02 -0700, John Bell <jbellnewsposts@.hotmail.com>
> wrote:
> >Hi
> >
> >I am not sure why this is not selecting your database when you right click!
> >Have you tried left clicking before you right click?
> >
> >An althernative you be to backup and restore the database into a new copy,
> >you can do this in a query window. If you need to do this often then creating
> >a script will probably end up being quicker.
> >
> >John
> >
> >"Les Caudle" wrote:
> >
> >> I connected to an sql 2005 located out on the Internet.
> >>
> >> I can export the database I have permissions for and its data ok.
> >>
> >> When I right click on the db and choose copy, I get an error at the end of the
> >> wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened because
> >> it is offline. Error 942.
> >>
> >> That database shows up in the managment console, and it is offline, but it is
> >> not the one I right clicked on to copy. I don't have permission to put that
> >> database online, just permissions for the one I want to copy.
> >>
> >> How can I resolve this?
> >> --
> >> Thanks in advance, Les Caudle
> >>
>
attempt to copy 2005 db ouside my network shows wrong db?
I connected to an sql 2005 located out on the Internet.
I can export the database I have permissions for and its data ok.
When I right click on the db and choose copy, I get an error at the end of
the
wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened bec
ause
it is offline. Error 942.
That database shows up in the managment console, and it is offline, but it i
s
not the one I right clicked on to copy. I don't have permission to put that
database online, just permissions for the one I want to copy.
How can I resolve this?
--
Thanks in advance, Les CaudleHi
I am not sure why this is not selecting your database when you right click!
Have you tried left clicking before you right click?
An althernative you be to backup and restore the database into a new copy,
you can do this in a query window. If you need to do this often then creatin
g
a script will probably end up being quicker.
John
"Les Caudle" wrote:
> I connected to an sql 2005 located out on the Internet.
> I can export the database I have permissions for and its data ok.
> When I right click on the db and choose copy, I get an error at the end o
f the
> wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened b
ecause
> it is offline. Error 942.
> That database shows up in the managment console, and it is offline, but it
is
> not the one I right clicked on to copy. I don't have permission to put th
at
> database online, just permissions for the one I want to copy.
> How can I resolve this?
> --
> Thanks in advance, Les Caudle
>|||Hi
I am not sure why this is not selecting your database when you right click!
Have you tried left clicking before you right click?
An althernative you be to backup and restore the database into a new copy,
you can do this in a query window. If you need to do this often then creatin
g
a script will probably end up being quicker.
John
"Les Caudle" wrote:
> I connected to an sql 2005 located out on the Internet.
> I can export the database I have permissions for and its data ok.
> When I right click on the db and choose copy, I get an error at the end o
f the
> wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened b
ecause
> it is offline. Error 942.
> That database shows up in the managment console, and it is offline, but it
is
> not the one I right clicked on to copy. I don't have permission to put th
at
> database online, just permissions for the one I want to copy.
> How can I resolve this?
> --
> Thanks in advance, Les Caudle
>|||John - Yes, I'd clicked on the database first. Very strange.
This is on a client's ISP's shared web server. I only have access to his
database - and am going to need to grab it.
Can I backup and restore in this circumstance - as you suggested? I think I
'm
going to be limited in what I can do.
Thanks, Les Caudle
On Sun, 25 Jun 2006 00:00:02 -0700, John Bell <jbellnewsposts@.hotmail.com>
wrote:
[vbcol=seagreen]
>Hi
>I am not sure why this is not selecting your database when you right click!
>Have you tried left clicking before you right click?
>An althernative you be to backup and restore the database into a new copy,
>you can do this in a query window. If you need to do this often then creati
ng
>a script will probably end up being quicker.
>John
>"Les Caudle" wrote:
>|||John - Yes, I'd clicked on the database first. Very strange.
This is on a client's ISP's shared web server. I only have access to his
database - and am going to need to grab it.
Can I backup and restore in this circumstance - as you suggested? I think I
'm
going to be limited in what I can do.
Thanks, Les Caudle
On Sun, 25 Jun 2006 00:00:02 -0700, John Bell <jbellnewsposts@.hotmail.com>
wrote:
[vbcol=seagreen]
>Hi
>I am not sure why this is not selecting your database when you right click!
>Have you tried left clicking before you right click?
>An althernative you be to backup and restore the database into a new copy,
>you can do this in a query window. If you need to do this often then creati
ng
>a script will probably end up being quicker.
>John
>"Les Caudle" wrote:
>|||Les Caudle wrote:
> John - Yes, I'd clicked on the database first. Very strange.
> This is on a client's ISP's shared web server. I only have access to his
> database - and am going to need to grab it.
> Can I backup and restore in this circumstance - as you suggested? I think
I'm
> going to be limited in what I can do.
>
Providing you can connect with Query Analyzer or Management Studio, and
have a directory that SQL can write to, you should be able to use the
BACKUP and RESTORE commands to do a backup and restore.|||Les Caudle wrote:
> John - Yes, I'd clicked on the database first. Very strange.
> This is on a client's ISP's shared web server. I only have access to his
> database - and am going to need to grab it.
> Can I backup and restore in this circumstance - as you suggested? I think
I'm
> going to be limited in what I can do.
>
Providing you can connect with Query Analyzer or Management Studio, and
have a directory that SQL can write to, you should be able to use the
BACKUP and RESTORE commands to do a backup and restore.|||Hi
To backup the datbase you will need in the db_backupoperator, db_owner or a
sysadmin role, for restoring you will need to be a sysadmin or in dbcreator
role.
To use sp_attach_db you will need CREATE DATABASE, CREATE ANY DATABASE, or
ALTER ANY DATABASE permission, for sp_detach_db you will need to be a
db_owner.
I suspect that the copy wizard may not be working because you fail on some
or all of these privileges. By doing a manual backup you may get a message
saying that you do not have the privileges to carry out the opertation.
John
"Les Caudle" wrote:
> John - Yes, I'd clicked on the database first. Very strange.
> This is on a client's ISP's shared web server. I only have access to his
> database - and am going to need to grab it.
> Can I backup and restore in this circumstance - as you suggested? I think
I'm
> going to be limited in what I can do.
> Thanks, Les Caudle
>
> On Sun, 25 Jun 2006 00:00:02 -0700, John Bell <jbellnewsposts@.hotmail.com>
> wrote:
>
>|||Hi
To backup the datbase you will need in the db_backupoperator, db_owner or a
sysadmin role, for restoring you will need to be a sysadmin or in dbcreator
role.
To use sp_attach_db you will need CREATE DATABASE, CREATE ANY DATABASE, or
ALTER ANY DATABASE permission, for sp_detach_db you will need to be a
db_owner.
I suspect that the copy wizard may not be working because you fail on some
or all of these privileges. By doing a manual backup you may get a message
saying that you do not have the privileges to carry out the opertation.
John
"Les Caudle" wrote:
> John - Yes, I'd clicked on the database first. Very strange.
> This is on a client's ISP's shared web server. I only have access to his
> database - and am going to need to grab it.
> Can I backup and restore in this circumstance - as you suggested? I think
I'm
> going to be limited in what I can do.
> Thanks, Les Caudle
>
> On Sun, 25 Jun 2006 00:00:02 -0700, John Bell <jbellnewsposts@.hotmail.com>
> wrote:
>
>
I can export the database I have permissions for and its data ok.
When I right click on the db and choose copy, I get an error at the end of
the
wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened bec
ause
it is offline. Error 942.
That database shows up in the managment console, and it is offline, but it i
s
not the one I right clicked on to copy. I don't have permission to put that
database online, just permissions for the one I want to copy.
How can I resolve this?
--
Thanks in advance, Les CaudleHi
I am not sure why this is not selecting your database when you right click!
Have you tried left clicking before you right click?
An althernative you be to backup and restore the database into a new copy,
you can do this in a query window. If you need to do this often then creatin
g
a script will probably end up being quicker.
John
"Les Caudle" wrote:
> I connected to an sql 2005 located out on the Internet.
> I can export the database I have permissions for and its data ok.
> When I right click on the db and choose copy, I get an error at the end o
f the
> wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened b
ecause
> it is offline. Error 942.
> That database shows up in the managment console, and it is offline, but it
is
> not the one I right clicked on to copy. I don't have permission to put th
at
> database online, just permissions for the one I want to copy.
> How can I resolve this?
> --
> Thanks in advance, Les Caudle
>|||Hi
I am not sure why this is not selecting your database when you right click!
Have you tried left clicking before you right click?
An althernative you be to backup and restore the database into a new copy,
you can do this in a query window. If you need to do this often then creatin
g
a script will probably end up being quicker.
John
"Les Caudle" wrote:
> I connected to an sql 2005 located out on the Internet.
> I can export the database I have permissions for and its data ok.
> When I right click on the db and choose copy, I get an error at the end o
f the
> wizard saying that Database 'dbThatIsDifferentThanMine' cannot be opened b
ecause
> it is offline. Error 942.
> That database shows up in the managment console, and it is offline, but it
is
> not the one I right clicked on to copy. I don't have permission to put th
at
> database online, just permissions for the one I want to copy.
> How can I resolve this?
> --
> Thanks in advance, Les Caudle
>|||John - Yes, I'd clicked on the database first. Very strange.
This is on a client's ISP's shared web server. I only have access to his
database - and am going to need to grab it.
Can I backup and restore in this circumstance - as you suggested? I think I
'm
going to be limited in what I can do.
Thanks, Les Caudle
On Sun, 25 Jun 2006 00:00:02 -0700, John Bell <jbellnewsposts@.hotmail.com>
wrote:
[vbcol=seagreen]
>Hi
>I am not sure why this is not selecting your database when you right click!
>Have you tried left clicking before you right click?
>An althernative you be to backup and restore the database into a new copy,
>you can do this in a query window. If you need to do this often then creati
ng
>a script will probably end up being quicker.
>John
>"Les Caudle" wrote:
>|||John - Yes, I'd clicked on the database first. Very strange.
This is on a client's ISP's shared web server. I only have access to his
database - and am going to need to grab it.
Can I backup and restore in this circumstance - as you suggested? I think I
'm
going to be limited in what I can do.
Thanks, Les Caudle
On Sun, 25 Jun 2006 00:00:02 -0700, John Bell <jbellnewsposts@.hotmail.com>
wrote:
[vbcol=seagreen]
>Hi
>I am not sure why this is not selecting your database when you right click!
>Have you tried left clicking before you right click?
>An althernative you be to backup and restore the database into a new copy,
>you can do this in a query window. If you need to do this often then creati
ng
>a script will probably end up being quicker.
>John
>"Les Caudle" wrote:
>|||Les Caudle wrote:
> John - Yes, I'd clicked on the database first. Very strange.
> This is on a client's ISP's shared web server. I only have access to his
> database - and am going to need to grab it.
> Can I backup and restore in this circumstance - as you suggested? I think
I'm
> going to be limited in what I can do.
>
Providing you can connect with Query Analyzer or Management Studio, and
have a directory that SQL can write to, you should be able to use the
BACKUP and RESTORE commands to do a backup and restore.|||Les Caudle wrote:
> John - Yes, I'd clicked on the database first. Very strange.
> This is on a client's ISP's shared web server. I only have access to his
> database - and am going to need to grab it.
> Can I backup and restore in this circumstance - as you suggested? I think
I'm
> going to be limited in what I can do.
>
Providing you can connect with Query Analyzer or Management Studio, and
have a directory that SQL can write to, you should be able to use the
BACKUP and RESTORE commands to do a backup and restore.|||Hi
To backup the datbase you will need in the db_backupoperator, db_owner or a
sysadmin role, for restoring you will need to be a sysadmin or in dbcreator
role.
To use sp_attach_db you will need CREATE DATABASE, CREATE ANY DATABASE, or
ALTER ANY DATABASE permission, for sp_detach_db you will need to be a
db_owner.
I suspect that the copy wizard may not be working because you fail on some
or all of these privileges. By doing a manual backup you may get a message
saying that you do not have the privileges to carry out the opertation.
John
"Les Caudle" wrote:
> John - Yes, I'd clicked on the database first. Very strange.
> This is on a client's ISP's shared web server. I only have access to his
> database - and am going to need to grab it.
> Can I backup and restore in this circumstance - as you suggested? I think
I'm
> going to be limited in what I can do.
> Thanks, Les Caudle
>
> On Sun, 25 Jun 2006 00:00:02 -0700, John Bell <jbellnewsposts@.hotmail.com>
> wrote:
>
>|||Hi
To backup the datbase you will need in the db_backupoperator, db_owner or a
sysadmin role, for restoring you will need to be a sysadmin or in dbcreator
role.
To use sp_attach_db you will need CREATE DATABASE, CREATE ANY DATABASE, or
ALTER ANY DATABASE permission, for sp_detach_db you will need to be a
db_owner.
I suspect that the copy wizard may not be working because you fail on some
or all of these privileges. By doing a manual backup you may get a message
saying that you do not have the privileges to carry out the opertation.
John
"Les Caudle" wrote:
> John - Yes, I'd clicked on the database first. Very strange.
> This is on a client's ISP's shared web server. I only have access to his
> database - and am going to need to grab it.
> Can I backup and restore in this circumstance - as you suggested? I think
I'm
> going to be limited in what I can do.
> Thanks, Les Caudle
>
> On Sun, 25 Jun 2006 00:00:02 -0700, John Bell <jbellnewsposts@.hotmail.com>
> wrote:
>
>
Subscribe to:
Posts (Atom)