I copied a database from my production server to the development server and now i dont see the users in the database from the enterprise manager,database and users folder. But, When i run a query to against the sysuser table from a query analyser I can see those users here. Why cant I see in from the Enterprise manager. Any advice please..
Hi, I wanted to see what are all the users in a windows nt group that has a group access to sql server 2000. I have a windows 2000 group access to sqlserver 2000 as "xxxsomegroup". How can I list all users that belongs to this windows 200 group? is there any stored procedure to find out this? any information could be greatly appreciated.
I have had this issue just pop up. I have local users who can connect fine, but my users that require connection by VPN cannot connect. I get the server not available or access denied error. I did confirm that the VPN'ers are connected to the network correctly and can see that their shares and mappings are correct. Any ideas? Thanking you all in advance!!
In a development server you take a backup and you want to move the entire database to a production server. The production server does not contain the database, users, or logins in master.
When you restore the backup to production in 7.0, the users get moved to DBO because the logins do not exist and then you cannot delete them.
We are having to drop the users from the database on development, back up the database and restore it to production, then recreate the users on production.
This is bogus and did not happen in 6.5 because of the aliases.
After replicating a database, the stored procedures in that same database are not able to edit by other users than service account (sys admin users), When the normal users try to edit any of the stored procedures, sql server 2005 is throwing the following error...
Msg 21050, Level 16, State 1, Procedure sp_MSmerge_ddldispatcher, Line 12Only members of the sysadmin fixed server role or db_owner fixed database role can perform this operation. Contact an administrator with sufficient permissions to perform this operation.
Does anyone know a way to force out all users from a particular database? I need to script this to perform some maintenance at a particular time every day.
Is there a way in SQL to drop any users from a database. I am trying to schedule some nightly DB maintenance and some users are still in there sometimes. I need to be able to kick the out to do dbcc checkdbs, etc. Is there a way for me to do this without stopping the SQL services?
I restored a database from one full backup.The users are missing now in the new databse.When I try to create the same users again it says that they are already existing!Please help what shall I do to restore/recreate the users?Do I need to do anything with the Master?
I have a question regarding copying users from one server to another that are running different versions of Microsoft Sequel Server.
I have Server A running 6.5 version and Server B running 7.0 version. How can I copy just the list of users from Database1 on Server A to Database2 on Server B.
Ok I created a database SQL is the engine and Access XP is the gui. When the users try to access the databae they get error message, it opens up but they cant open the forms for some reason. I was wondering if this had to do with me have Access XP and them having Access 2000, but I highly doubt it because when I had a user log on to my machine (which has access xp) they still were not able to access the forms. Can someone help me out PLEASE PLEASE PLEASE... this is so frustrating :(
One thing I'm noticing is that the users connection keeps dropping???
I have a number of user databases who have lost their owner. That is, displaying properties for the database says the owner is unknown.
I assume that any user for such a database that's assigned to the db_owner role can admin everything in this database? Which means that the lack of a dbo doesn't cause any other problem than making it impossible to run a sp_helpdb for the database, or...?
Of course I'd like to make someone the owner, but it seems difficult to make an already existing database user the owner, without dropping the user and re-creating it.
Ok I just installed SQl 2005 for the very first time. I used a service account(domain admin)and Windows NT authentication to install SQL.
Now I am setting up Mcafee EPO on a different server. This application can either install MSDE or use a sql database. I want to use my new SQL server.
What are the best practices to : a)create database on SQL b)create a user c)what permissions to give this user
For example during installation of Mcafee EPO it is asking me name of the remote SQL server, authentication method(Windows or SQL)and the user account.
I am starting to read about SQL but need some quick answers. I need to do the same thing for my SMS 2003 installation. Thanks.
As a newbie to DBA type tasks, how can I trace who has accessed the server/database. I know there is a SPID in the Server log but what does this represent?
I am an advanced user of MS Access and other databases but relatively new to SQL Server. I am utilizing SQL Server Express to analyze a database that was created by another entity. I am interested in looking at any specific record in any table and seeing who created that record, what date/time the record was created, who edited the record, when that edit occurred, etc. I don't see any such fields in the database. Would the designer of the database have to have explicitly added such functionality, or is this information available but just hidden from the novice's view?
Alrighty.... I'm a long time listener and a first time caller here. I've been reading multiple topics dealing with my issue but none seem to really address what I'm doing.
We have 3 separate enviroments, Dev, QA, and Prod. Quite frequently we have a database that gets moved from our Dev Server to QA, or QA to Prod, or Prod to QA ect...
What we have been doing is when a database is moved, it holds all of the actual database logins, but when you look within the actual server logins there's nothing there (dealing w/ that specific database). So we then have to go first through all of our logins on the database write them down, then go one by one and create them on the server.
I'm wondering if there is a more simple way to be doing this to cut down on our administration time?
3/4 of our ID's on the database are all linked through our Domain using windows authentication. And since we keep all of our "application/local SQL ID's" enviromentally separate. (each ID XXX has its own ID for Dev, QA and Prod... XXXdev, XXXqa, and XXXprod) so we'll have to do those manually anyways, but I'm really hoping someone has a solution to this timely administration process!
Thanks for all of your help! -Randy
Information Security Analyst Securian Financial Group St.Paul Mn,
"When you do things right, people won't be sure you've done anything at all." Bender Bending RodrÃguez - Futurama
I can't figure out what the purpose of having seperate users is as I can't actually login to the database using one.
Here is my scenario.
I have a single login called LoginA and I have a database which I want to carve up using schema's. At the database level I need to create a user, associate a login with this user and can set a default schema and specifiy what schemas this USER can access. The login created can access multiple schemas.
So..
I created a database login called loginA.
I created a user for the database called UserA set it's login name to LoginA and
I then created 3 schemas called SchemaA, SchemaB and SchemaC and set their schema owner name to UserA.
I went back to UserA and set their default Schema to SchemaA
How can I login using the new user created as it has no password associated with it. If I login using LoginA then I have no default Schema set becuase the schema is associated with a USER not a LOGIN.
I can understand why you can only have one login account assicated with one user account for each database but I can;t understand why you can specify a user name if you can't use it to login.
I have a question, Does anyone have a TSQL command the will log off ALL users connected to s specific database. The reason I ask is I have a database the needs all users logged off so Rules update can run.
The package I'm speaking of is Compulaw a court docketing database application, the system now performs a rules set update every morning, but will only run when no one is connected to that database. Any ideas?
I need help getting all the users that are "attached" or "allowed" to access a given database and their login information. I do not know if this is even possible but I had tried to do my own research and cant figure it out/find any info on it. Any help is greatly appreciated!
We have an existing SSRS server, and have just created a new child domain. We'll be migrating users from the parent to the child, and want to add the users of that new domain with access to SSRS. In the parent domain they are able to access, but after migration with the child domain account, they cannot.
I have added the group CHILDDomain Users with a system user role on SSRS, and PARENTDomain Users was already there.
Is there any additional step I should/could take to get this active?
Hi I'm trying to script an Admin user into my SQL set up scripts. I'm ok with creating the database, adding tables and populating the tables I've created and thought that I could just EXEC aspnet_Membership_CreateUser '/', 'Admin', 'SecretPassword'...to achieve my goal, but it seems that the framework is responsible for encrypting the password before it gets to the Procedure and clear text just isn't acceptable.Any ideas on how to go about adding the user through SQL?
Hi, i have a new site built in .net using the login/membership system. i have a legacy database (access) of users from the previous site with email, name, password, etc.Is it possible to import this data straight into my new membership tables through some insert statement, software or through some other way?
Hi, this is a bit of background to what I'm trying to achive: I have an application that creates a new database in MS 2000. The application will then create a login, with then create a user and add the login to the user, it will then add that user to the folling roles; db_owner, db_datareader, db_datawriter. A SQL script is then run to add tables, view and stored procedures to the new database. Most of this works however I'm having a few problems with loging in as the new user. Aslo how do I ensure that if new objects (tables, stored procs etc) are added the new user will have full permissions on them? This is the code I have so far...I'm going round in circles with it and was hoping that someone with fresh eyes might be able to see where I'm going wrong: Many thanks 1 protected string CreateUser(string strDatabaseName) 2 { 3 //database hase alreday been created 4 SQLDMO.SQLServer gSQLServerDMO = new SQLDMO.SQLServer(); 5 6 string serverName = ConfigurationManager.AppSettings["DbsServerName"]; 7 gSQLServerDMO.Connect(serverName, 8 ConfigurationManager.AppSettings["DbsUserName"], 9 ConfigurationManager.AppSettings["DbsUserPwd"]); 10 //get the database object 11 SQLDMO.Database dbs = (SQLDMO.Database)gSQLServerDMO.Databases.Item(strDatabaseName, ""); 12 13 #region create a login object and populate it 14 SQLDMO.Login login = new SQLDMO.Login(); 15 string loginName = strDatabaseName + "_WebLogin"; 16 login.Name = loginName; 17 string password = "password"; 18 19 login.SetPassword("", password); 20 login.Database = strDatabaseName; 21 22 //check if it exists 23 bool found = false; 24 foreach (SQLDMO.Login ologin in gSQLServerDMO.Logins) 25 { 26 if (ologin.Name == loginName) 27 { 28 found = true; 29 break; 30 } 31 } 32 if (!found) 33 gSQLServerDMO.Logins.Add(login); 34 #endregion 35 36 #region create the user 37 SQLDMO.User user = new SQLDMO.User(); 38 //assign the login 39 string userName = strDatabaseName+ "_WebUser"; 40 user.Name = userName; 41 user.Login = loginName; 42 //dbs.Users.Add(user); 43 44 found = false; 45 foreach (SQLDMO.User oUser in dbs.Users) 46 { 47 if (oUser.Name == loginName) 48 { 49 found = true; 50 break; 51 } 52 } 53 if (!found)//add the user to the dbs 54 { 55 dbs.Users.Add(user); 56 57 //add user to role 58 //db_owner 59 //SQLDMO.DatabaseRole oRole = new SQLDMO.DatabaseRole(); 60 //oRole = 61 //oRole.AddMember(loginName); 62 dbs.DatabaseRoles.Item("db_owner").AddMember(userName); 63 dbs.DatabaseRoles.Item("db_datareader").AddMember(userName); 64 dbs.DatabaseRoles.Item("db_datawriter").AddMember(userName); 65 } 66 #endregion 67 68 string connString = "server=" + serverName + ";database=" + strDatabaseName + ";uid=" + userName 69 + ";pwd=" + password + ";";
I'm developing an application in ASP.Net that uses SQLServer. The database person in the team wants to have each user have a seperate login to the database so he can tell who has done what changes in the database. Is this a good practice? Or are their performancesecurity issues with this model?
I backed up and restored a database successfully except for the users. The only user that shows is dbo, but I can't add a user with the proper user name from my old server; I get the error that the user or role already exists in the current database.
When I go to role, name of public, there is the user I need to add. I can't remove it as it's a table owner, but I need to add it to the list of users, so I need to remove it then re-add it.
I tried using EXEC sp_changeobjectowner to no avail.