New to SQL and Web development

I have been in systems for many years on the admin side, and have had experience working with developers, however I am attempting to start the learning process for creating a data store with a web based UI. I have an understanding of the theories of what
is possible, but I don't know where to start. I have experience with HTML coding and static pages, but nothing that interfaces with a back end.
What are your suggestions of where to start.
This is a great site with lots of good answers to many questions:
http://www.aspfaq.com/
You will find good examples and information out on =
http://www.asp101.com/
--=20
Keith
"Otts73" <sh_tmail@.charter.net> wrote in message =
news:EFF6B423-F1FA-41D1-9139-3929979CCB3F@.microsoft.com...
> I have been in systems for many years on the admin side, and have had =
experience working with developers, however I am attempting to start the =
learning process for creating a data store with a web based UI. I have =
an understanding of the theories of what is possible, but I don't know =
where to start. I have experience with HTML coding and static pages, =
but nothing that interfaces with a back end.
>=20
> What are your suggestions of where to start.
|||As well as Keith's references, you might like to look at
http://www.w3schools.com/ado/default.asp
Regards,
Paul Ibison

New to SQL and Web development

I have been in systems for many years on the admin side, and have had experi
ence working with developers, however I am attempting to start the learning
process for creating a data store with a web based UI. I have an understand
ing of the theories of what
is possible, but I don't know where to start. I have experience with HTML c
oding and static pages, but nothing that interfaces with a back end.
What are your suggestions of where to start.This is a great site with lots of good answers to many questions:
http://www.aspfaq.com/
You will find good examples and information out on =
http://www.asp101.com/
--=20
Keith
"Otts73" <sh_tmail@.charter.net> wrote in message =
news:EFF6B423-F1FA-41D1-9139-3929979CCB3F@.microsoft.com...
> I have been in systems for many years on the admin side, and have had =
experience working with developers, however I am attempting to start the =
learning process for creating a data store with a web based UI. I have =
an understanding of the theories of what is possible, but I don't know =
where to start. I have experience with HTML coding and static pages, =
but nothing that interfaces with a back end.
>=20
> What are your suggestions of where to start.|||As well as Keith's references, you might like to look at
http://www.w3schools.com/ado/default.asp
Regards,
Paul Ibison

New to SQL and Web development

I have been in systems for many years on the admin side, and have had experience working with developers, however I am attempting to start the learning process for creating a data store with a web based UI. I have an understanding of the theories of what is possible, but I don't know where to start. I have experience with HTML coding and static pages, but nothing that interfaces with a back end
What are your suggestions of where to start.This is a great site with lots of good answers to many questions:
http://www.aspfaq.com/
You will find good examples and information out on =http://www.asp101.com/
-- Keith
"Otts73" <sh_tmail@.charter.net> wrote in message =news:EFF6B423-F1FA-41D1-9139-3929979CCB3F@.microsoft.com...
> I have been in systems for many years on the admin side, and have had =experience working with developers, however I am attempting to start the =learning process for creating a data store with a web based UI. I have =an understanding of the theories of what is possible, but I don't know =where to start. I have experience with HTML coding and static pages, =but nothing that interfaces with a back end.
> > What are your suggestions of where to start.|||As well as Keith's references, you might like to look at
http://www.w3schools.com/ado/default.asp
Regards,
Paul Ibisonsql

New to SQL 2005, need a little help

I come from a Sys Admin background so excuse my questions if their
simple in nature.
Anyways we purchase an e-mail system at our company that uses SQL
server as it's database. In the documentation, it states I need to
create a SQL account and give it a specific username and password. I
can create the account, but it doesn't ask for a password. Do SQL
account's usually have passwords, or could they be referring to the SA
password I used when installing SQL? Also, when creating a SQL account,
it asks for a user name and login name. I can specify the user name,
but I can only select from a small list login name's to use. If someone
can clarify what the login name is exactly I'd appreciate it (i believe
it's the windows security account which sql uses to gain access to the
server but i dont know).
Thanksbdhenderson@.gmail.com wrote:
> I come from a Sys Admin background so excuse my questions if their
> simple in nature.
> Anyways we purchase an e-mail system at our company that uses SQL
> server as it's database. In the documentation, it states I need to
> create a SQL account and give it a specific username and password. I
> can create the account, but it doesn't ask for a password. Do SQL
> account's usually have passwords, or could they be referring to the SA
> password I used when installing SQL? Also, when creating a SQL account,
> it asks for a user name and login name. I can specify the user name,
> but I can only select from a small list login name's to use. If someone
> can clarify what the login name is exactly I'd appreciate it (i believe
> it's the windows security account which sql uses to gain access to the
> server but i dont know).
> Thanks
>
You are creating Windows Authentication logins, not SQL logins. SQL
Server supports both.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||It might be useful for you to know more about SQL Server Security.
From SQL Server Management Studio, click on [Help], then [Contents], then
[SQL Server Books on Line], and find the topic [Security Considerations for
SQL Server]
--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
<bdhenderson@.gmail.com> wrote in message
news:1152796948.762797.20070@.h48g2000cwc.googlegroups.com...
>I come from a Sys Admin background so excuse my questions if their
> simple in nature.
> Anyways we purchase an e-mail system at our company that uses SQL
> server as it's database. In the documentation, it states I need to
> create a SQL account and give it a specific username and password. I
> can create the account, but it doesn't ask for a password. Do SQL
> account's usually have passwords, or could they be referring to the SA
> password I used when installing SQL? Also, when creating a SQL account,
> it asks for a user name and login name. I can specify the user name,
> but I can only select from a small list login name's to use. If someone
> can clarify what the login name is exactly I'd appreciate it (i believe
> it's the windows security account which sql uses to gain access to the
> server but i dont know).
> Thanks
>|||I think you are in the wrong section of the GUI. From what you
described in the GUI you connected to a server, and opened databases,
then opened a database, then opened security. You then right clicked
and selected new user.
What you actually need to do it after connecting to the server, leave
the databases folder closed. You should see a security folder. Open
that up, this will allow you to create a login and assign it a
password.
SQL Server has logins and users. Logins have passwords and allow you
to log into the database. Users are mapped to a login and give you the
right to see inside a single database on the server.
Denny
bdhenderson@.gmail.com wrote:
> I come from a Sys Admin background so excuse my questions if their
> simple in nature.
> Anyways we purchase an e-mail system at our company that uses SQL
> server as it's database. In the documentation, it states I need to
> create a SQL account and give it a specific username and password. I
> can create the account, but it doesn't ask for a password. Do SQL
> account's usually have passwords, or could they be referring to the SA
> password I used when installing SQL? Also, when creating a SQL account,
> it asks for a user name and login name. I can specify the user name,
> but I can only select from a small list login name's to use. If someone
> can clarify what the login name is exactly I'd appreciate it (i believe
> it's the windows security account which sql uses to gain access to the
> server but i dont know).
> Thankssql

New to SQL 2005, need a little help

I come from a Sys Admin background so excuse my questions if their
simple in nature.
Anyways we purchase an e-mail system at our company that uses SQL
server as it's database. In the documentation, it states I need to
create a SQL account and give it a specific username and password. I
can create the account, but it doesn't ask for a password. Do SQL
account's usually have passwords, or could they be referring to the SA
password I used when installing SQL? Also, when creating a SQL account,
it asks for a user name and login name. I can specify the user name,
but I can only select from a small list login name's to use. If someone
can clarify what the login name is exactly I'd appreciate it (i believe
it's the windows security account which sql uses to gain access to the
server but i dont know).
Thanksbdhenderson@.gmail.com wrote:
> I come from a Sys Admin background so excuse my questions if their
> simple in nature.
> Anyways we purchase an e-mail system at our company that uses SQL
> server as it's database. In the documentation, it states I need to
> create a SQL account and give it a specific username and password. I
> can create the account, but it doesn't ask for a password. Do SQL
> account's usually have passwords, or could they be referring to the SA
> password I used when installing SQL? Also, when creating a SQL account,
> it asks for a user name and login name. I can specify the user name,
> but I can only select from a small list login name's to use. If someone
> can clarify what the login name is exactly I'd appreciate it (i believe
> it's the windows security account which sql uses to gain access to the
> server but i dont know).
> Thanks
>
You are creating Windows Authentication logins, not SQL logins. SQL
Server supports both.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||It might be useful for you to know more about SQL Server Security.
From SQL Server Management Studio, click on [Help], then [Contents],
then
[SQL Server Books on Line], and find the topic [Security Considerati
ons for
SQL Server]
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
<bdhenderson@.gmail.com> wrote in message
news:1152796948.762797.20070@.h48g2000cwc.googlegroups.com...
>I come from a Sys Admin background so excuse my questions if their
> simple in nature.
> Anyways we purchase an e-mail system at our company that uses SQL
> server as it's database. In the documentation, it states I need to
> create a SQL account and give it a specific username and password. I
> can create the account, but it doesn't ask for a password. Do SQL
> account's usually have passwords, or could they be referring to the SA
> password I used when installing SQL? Also, when creating a SQL account,
> it asks for a user name and login name. I can specify the user name,
> but I can only select from a small list login name's to use. If someone
> can clarify what the login name is exactly I'd appreciate it (i believe
> it's the windows security account which sql uses to gain access to the
> server but i dont know).
> Thanks
>|||I think you are in the wrong section of the GUI. From what you
described in the GUI you connected to a server, and opened databases,
then opened a database, then opened security. You then right clicked
and selected new user.
What you actually need to do it after connecting to the server, leave
the databases folder closed. You should see a security folder. Open
that up, this will allow you to create a login and assign it a
password.
SQL Server has logins and users. Logins have passwords and allow you
to log into the database. Users are mapped to a login and give you the
right to see inside a single database on the server.
Denny
bdhenderson@.gmail.com wrote:
> I come from a Sys Admin background so excuse my questions if their
> simple in nature.
> Anyways we purchase an e-mail system at our company that uses SQL
> server as it's database. In the documentation, it states I need to
> create a SQL account and give it a specific username and password. I
> can create the account, but it doesn't ask for a password. Do SQL
> account's usually have passwords, or could they be referring to the SA
> password I used when installing SQL? Also, when creating a SQL account,
> it asks for a user name and login name. I can specify the user name,
> but I can only select from a small list login name's to use. If someone
> can clarify what the login name is exactly I'd appreciate it (i believe
> it's the windows security account which sql uses to gain access to the
> server but i dont know).
> Thanks

new sql login using active directory

I have a sql admin who is not a domain admin and when he selects a new login for sql 2000 using the domain lookup it tells him he has no permission and can't see any user in active directory. He does have active directory users and computers on his desktop and can see them all there. Any suggestions' He is a local admin on the sql server box and can see local users.I would think you can't enumerate users and groups in
Active Directory unless you are given specific rights. I
know this is true for Open LDAP and IBM SecureWay bases
directory services. Ask him to enter NET USERS /DOMAIN
command on DOS command prompt and see if it lists all
users in the Domain. I would suggest you to post this
question to windows 2000 group, or ask your network admin.
This isn't a sql issue, if he is local admin then more
likely he has DBA privileges in server.
>--Original Message--
>I have a sql admin who is not a domain admin and when he
selects a new login for sql 2000 using the domain lookup
it tells him he has no permission and can't see any user
in active directory. He does have active directory users
and computers on his desktop and can see them all there.
Any suggestions' He is a local admin on the sql
server box and can see local users.
>.
>

new login, EXECUTE permissions

I'm a newbie to the admin side of SqlServer. I created a new login:
<code>
CREATE LOGIN pmd_app
WITH PASSWORD='********'
</code>
I then used the "Server Management Studio Express" to create a new user in
my DB with the same name, then give the logical permissions, at least
logical to me. I can read and write table data with this new user, but I'm
getting EXECUTE permission errors when calling sprocs. I know how to grant
permissions to a user on a per object basis, but what role memberships
should I be using to give them EXECUTE permissions to all new sprocs that I
create?
I'm looking over BOL to see if I can find the answer, but so far not coming
up with anything.
Also, if anyone knows a good place to find an article covering SQLServer
security, role, permission, schemas, etc that would be awesome ;)
Thanks for any help,
Steve> getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships
If the user is an owner of the object he/she has an EXECUTE permissions
automatically.
Who is the owner of the object?
"sklett" <sklett@.mddirect.com> wrote in message
news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but
> I'm getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships should I be using to give them EXECUTE permissions to all new
> sprocs that I create?
> I'm looking over BOL to see if I can find the answer, but so far not
> coming up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>|||That's a 2000 way of thinking. The new way is to associate everything via
schemas.
Create a schema, grant your users execute permissions in the schema, create
all you new procs under that schema...easy!
"sklett" wrote:
> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but I'm
> getting EXECUTE permission errors when calling sprocs. I know how to grant
> permissions to a user on a per object basis, but what role memberships
> should I be using to give them EXECUTE permissions to all new sprocs that I
> create?
> I'm looking over BOL to see if I can find the answer, but so far not coming
> up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>
>|||oooh, uncharted territory! - scary and exciting :)
So it sounds like I need to put my tools down and read the manual. I will
do some Schema research and figure just how they work and what they do.
Thanks for the tip!
"mulhall" <mulhall@.discussions.microsoft.com> wrote in message
news:C6F5B46D-52D0-4EC2-9782-A72A53774A26@.microsoft.com...
> That's a 2000 way of thinking. The new way is to associate everything via
> schemas.
> Create a schema, grant your users execute permissions in the schema,
> create
> all you new procs under that schema...easy!
> "sklett" wrote:
>> I'm a newbie to the admin side of SqlServer. I created a new login:
>> <code>
>> CREATE LOGIN pmd_app
>> WITH PASSWORD='********'
>> </code>
>>
>> I then used the "Server Management Studio Express" to create a new user
>> in
>> my DB with the same name, then give the logical permissions, at least
>> logical to me. I can read and write table data with this new user, but
>> I'm
>> getting EXECUTE permission errors when calling sprocs. I know how to
>> grant
>> permissions to a user on a per object basis, but what role memberships
>> should I be using to give them EXECUTE permissions to all new sprocs that
>> I
>> create?
>> I'm looking over BOL to see if I can find the answer, but so far not
>> coming
>> up with anything.
>> Also, if anyone knows a good place to find an article covering SQLServer
>> security, role, permission, schemas, etc that would be awesome ;)
>> Thanks for any help,
>> Steve
>>|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uBW9KT4NGHA.1460@.TK2MSFTNGP10.phx.gbl...
>> getting EXECUTE permission errors when calling sprocs. I know how to
>> grant permissions to a user on a per object basis, but what role
>> memberships
> If the user is an owner of the object he/she has an EXECUTE permissions
> automatically.
> Who is the owner of the object?
I don't know :)
if the full name of the object is any indicator ("dbo.usp_MySprocName") I
would have to guess 'dbo' - but I could be wrong. Schemas are brand new to
me, I don't know whay they are or how they work.
Looking at the already defined schemas in my DB, I don't see any obvious
ones that would indicate EXECUTE permissions, I may need to make my own?
Sounds like schemas are my solution, I need to learn about them. Thanks for
the post!
-Steve
>
> "sklett" <sklett@.mddirect.com> wrote in message
> news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
>> I'm a newbie to the admin side of SqlServer. I created a new login:
>> <code>
>> CREATE LOGIN pmd_app
>> WITH PASSWORD='********'
>> </code>
>>
>> I then used the "Server Management Studio Express" to create a new user
>> in my DB with the same name, then give the logical permissions, at least
>> logical to me. I can read and write table data with this new user, but
>> I'm getting EXECUTE permission errors when calling sprocs. I know how to
>> grant permissions to a user on a per object basis, but what role
>> memberships should I be using to give them EXECUTE permissions to all new
>> sprocs that I create?
>> I'm looking over BOL to see if I can find the answer, but so far not
>> coming up with anything.
>> Also, if anyone knows a good place to find an article covering SQLServer
>> security, role, permission, schemas, etc that would be awesome ;)
>> Thanks for any help,
>> Steve
>

new login, EXECUTE permissions

I'm a newbie to the admin side of SqlServer. I created a new login:
<code>
CREATE LOGIN pmd_app
WITH PASSWORD='********'
</code>
I then used the "Server Management Studio Express" to create a new user in
my DB with the same name, then give the logical permissions, at least
logical to me. I can read and write table data with this new user, but I'm
getting EXECUTE permission errors when calling sprocs. I know how to grant
permissions to a user on a per object basis, but what role memberships
should I be using to give them EXECUTE permissions to all new sprocs that I
create?
I'm looking over BOL to see if I can find the answer, but so far not coming
up with anything.
Also, if anyone knows a good place to find an article covering SQLServer
security, role, permission, schemas, etc that would be awesome ;)
Thanks for any help,
Steve
> getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships
If the user is an owner of the object he/she has an EXECUTE permissions
automatically.
Who is the owner of the object?
"sklett" <sklett@.mddirect.com> wrote in message
news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but
> I'm getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships should I be using to give them EXECUTE permissions to all new
> sprocs that I create?
> I'm looking over BOL to see if I can find the answer, but so far not
> coming up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>
|||That's a 2000 way of thinking. The new way is to associate everything via
schemas.
Create a schema, grant your users execute permissions in the schema, create
all you new procs under that schema...easy!
"sklett" wrote:

> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but I'm
> getting EXECUTE permission errors when calling sprocs. I know how to grant
> permissions to a user on a per object basis, but what role memberships
> should I be using to give them EXECUTE permissions to all new sprocs that I
> create?
> I'm looking over BOL to see if I can find the answer, but so far not coming
> up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>
>
|||oooh, uncharted territory! - scary and exciting
So it sounds like I need to put my tools down and read the manual. I will
do some Schema research and figure just how they work and what they do.
Thanks for the tip!
"mulhall" <mulhall@.discussions.microsoft.com> wrote in message
news:C6F5B46D-52D0-4EC2-9782-A72A53774A26@.microsoft.com...[vbcol=seagreen]
> That's a 2000 way of thinking. The new way is to associate everything via
> schemas.
> Create a schema, grant your users execute permissions in the schema,
> create
> all you new procs under that schema...easy!
> "sklett" wrote:
|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uBW9KT4NGHA.1460@.TK2MSFTNGP10.phx.gbl...
> If the user is an owner of the object he/she has an EXECUTE permissions
> automatically.
> Who is the owner of the object?
I don't know
if the full name of the object is any indicator ("dbo.usp_MySprocName") I
would have to guess 'dbo' - but I could be wrong. Schemas are brand new to
me, I don't know whay they are or how they work.
Looking at the already defined schemas in my DB, I don't see any obvious
ones that would indicate EXECUTE permissions, I may need to make my own?
Sounds like schemas are my solution, I need to learn about them. Thanks for
the post!
-Steve

>
> "sklett" <sklett@.mddirect.com> wrote in message
> news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
>

new login, EXECUTE permissions

I'm a newbie to the admin side of SqlServer. I created a new login:
<code>
CREATE LOGIN pmd_app
WITH PASSWORD='********'
</code>
I then used the "Server Management Studio Express" to create a new user in
my DB with the same name, then give the logical permissions, at least
logical to me. I can read and write table data with this new user, but I'm
getting EXECUTE permission errors when calling sprocs. I know how to grant
permissions to a user on a per object basis, but what role memberships
should I be using to give them EXECUTE permissions to all new sprocs that I
create?
I'm looking over BOL to see if I can find the answer, but so far not coming
up with anything.
Also, if anyone knows a good place to find an article covering SQLServer
security, role, permission, schemas, etc that would be awesome ;)
Thanks for any help,
Steve> getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships
If the user is an owner of the object he/she has an EXECUTE permissions
automatically.
Who is the owner of the object?
"sklett" <sklett@.mddirect.com> wrote in message
news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but
> I'm getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships should I be using to give them EXECUTE permissions to all new
> sprocs that I create?
> I'm looking over BOL to see if I can find the answer, but so far not
> coming up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>|||That's a 2000 way of thinking. The new way is to associate everything via
schemas.
Create a schema, grant your users execute permissions in the schema, create
all you new procs under that schema...easy!
"sklett" wrote:

> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but I'
m
> getting EXECUTE permission errors when calling sprocs. I know how to gran
t
> permissions to a user on a per object basis, but what role memberships
> should I be using to give them EXECUTE permissions to all new sprocs that
I
> create?
> I'm looking over BOL to see if I can find the answer, but so far not comin
g
> up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>
>|||oooh, uncharted territory! - scary and exciting
So it sounds like I need to put my tools down and read the manual. I will
do some Schema research and figure just how they work and what they do.
Thanks for the tip!
"mulhall" <mulhall@.discussions.microsoft.com> wrote in message
news:C6F5B46D-52D0-4EC2-9782-A72A53774A26@.microsoft.com...[vbcol=seagreen]
> That's a 2000 way of thinking. The new way is to associate everything via
> schemas.
> Create a schema, grant your users execute permissions in the schema,
> create
> all you new procs under that schema...easy!
> "sklett" wrote:
>|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uBW9KT4NGHA.1460@.TK2MSFTNGP10.phx.gbl...
> If the user is an owner of the object he/she has an EXECUTE permissions
> automatically.
> Who is the owner of the object?
I don't know
if the full name of the object is any indicator ("dbo.usp_MySprocName") I
would have to guess 'dbo' - but I could be wrong. Schemas are brand new to
me, I don't know whay they are or how they work.
Looking at the already defined schemas in my DB, I don't see any obvious
ones that would indicate EXECUTE permissions, I may need to make my own?
Sounds like schemas are my solution, I need to learn about them. Thanks for
the post!
-Steve

>
> "sklett" <sklett@.mddirect.com> wrote in message
> news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
>

New Database: Best Practice

Good Morning,

I work for a company that has sees alot of people come and go. The one thing I have noticed is that people use their admin accounts to log into SQL and create sp, views and databases.When the user leaves I am stuck with all these objects that are owned by somone no longer working for the company.

So my question to you guys is: What is the best practice to use in creating new objects?

Thanks for your guru-ness!

When you create objects make sure to use the prefix "dbo.". Example: Create procedure dbo.uspSomeProc|||

Makes alot of sense. Now let me ask you this:

How would you keep track of who build what? Is there a way that procedure dbo.whatEverProc was created by me?

|||You can always drop/recreate the proc with dbo as the prefix. Alternatively you can check objects owned by a user thru this undocumented proc :sp_MScheck_uid_owns_anything @.uid