Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
duanecwilson
Constraint Violating Yak Guru
273 Posts |
 Posted - 2009-06-02 : 16:57:12
|
| I have gotten myself sufficiently confused that I need some guidance. I have been hired more or less as a dba for SQL Server 2005. One of my main jobs will be converting reports from an application called Misys that uses SQL Server as a back end (like Access pass-through queries). I have been issued a login that at first I used to create a different database. As far as I know, my login is windows authentication and I think I have permissions to everything so permissions is not an issue.But, I need to be brought up to speed on some things. I thought to create a schema such as .rpt so I could create some views that wouldn't get mixed up with all the other views already created. These views will use the existing views and tables (which are dbo) much as Misys already does somehow.But I have gotten confused on what to create first. I have a login now. Do I create another login to create these views? And then, how does a user differ from a login, and do I create the user first? I have heard that a user is or can be associated with a login. What's the difference? Does a user "login" the same way as a login does? And then, what about roles and schemas? Do I create a role, then a schema, then a user? What order. I have kind of been going in circles. I would start one of those and come to a screen where it is looking for an object name of some sorts. I would like to create a user that would use a schema to create objects that would run against the .dbo schema. Thanks for any hints.Duane |
|
|
duanecwilson
Constraint Violating Yak Guru
273 Posts |
Posted - 2009-06-03 : 17:23:11
|
| I could really use some help in this, just some basic, beginner guidance. Thank you.Duane |
 |
|
|
|
|
|
|
|
Creating logins, users, schemas, roles, etc.