I coding an ASP.NET app. I'm getting some error messages about the ASPNET user can't access the DB. How can I manage a user (specifically add one) in SQL Server 2000? Thanks in advance for your help!
I have a user that I have granted the server role "securityadministrator" and a database role "db_securityadmin". When logged inas this user I can create new logins but not run sp_adduser to add thenew login to as this says I don't have permission to do this. I canhowever run sp_revokedbaccess to get rid of a user from the database.
We have a 2-tier architecture with thick client (.NET 2.0) applications directly accessing the SQL Server database. We are struggling to manage lots of users while maintaining security. Granting lots of users directly to the database seems to be tough to manage. In fact, we would like to let supervisors without DBA previlege to add and remove users of our applications. Using SQL Authentication (a single account to access the database) is the other alternative but it is not considered as a secure solution.
I would appreciate if anyone gives me suggestions on how to handle this, without moving to a 3-tier architecture (dedicated middle-tier DB access layer running a custom user account).
Hi all,What are the fundamentals (fundamental functions) that most small tomedium sized organizations that use MS SQL Server 7 or 2000 valuemost?What's your insight?OK, here's my biased definition of small to medium sized organization,annual revenue from 20m to 300m.Thanks.DL
I also migrated the server level logins using SSIS transfer logins task, available on SSIS 'Transfer logins', I selected all the databases that I have migrated so that I have all database users account in server logins (to avoid orphaned users); but I don't have all the database users in server logins, also the sys.sysusers doesn't have the database users, that I have moved to SQL 2005. Can anybody help?
Also do I need to back up the SQL Server 2000 database and restore it on SQL 2005? What impact this operation can have?
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 SQL server admin id and password, and I want to do some create/delete new database, or mimium do some select statements. What do I need to install on my workstation in order to connect to SQL server remotely? What's the equivalent tools as SQLPlus in Oracle?
I am no longer able to manage SQL Server at the server explorer in Visual studio. i.e. create, modify and delete for Diagrams, Tables, Views, Stored Procs & Functions. Further more, it missing Diagram and function folder. I can only view or read data.
Hopefully a simple question: Is it possible to use Maintenance Plans created on SQL Server Management Studio (installed as part of an instance of SQL Server 2005 Standard Ed.) to back up databases running on an instance of SQL Server Express Edition with Advanced Services? I don't need directions, just whether or not it is permitted.
I've been able to create the plans including establishing connections to from SSMS to the the SQL Express instance, but they keep erroring out. I just need to know if this is actually permitted since Maintenance Plans are not available on Management Studio Express Edition.
I have installed a new SQL 2005 server and successfully moved a db from one to the other. The users from that db were also imported, but the system security was not. Users cannot access the SQL system to even attempt to login to the db. What am I missing to import/transfer/migrate the system logins from SQL2000 to SQL2005?
I am using SQL Server 2000. I am working on a project where there will be multiple databases on a single instance of SQL Server. Each database will have the exact same schema but will be accessed by different groups of users. What is the easiest way to sychronize changes between the databases, so that if I add a column to one database, it will be reflected in the other databases. If I add, remove, or alter a stored procedure, I want the change to be made in the other databases. I want the data in each database to remain isolated. In other words, I do not want replication of the data, only the schema of the databases. I would like to have a single "master" database that I use to make any schema changes and all the other databases be schema mirrors of this database each with their own data. I have looked into SQL Server replication, but this didn't seem to work the way I wanted and I wasn't able to publish column changes etc.
We recently moved our SQL Server 7.0 database from one machine to another, and I think the guys who did it didn't do things quite right...
None of the DTS packages work anymore.... the little lines (for lack of better terms here..) that contain the SQL statements and such, well, if I try to edit the properties of them, I get an error that says this: Error Source: Microsoft OLD DB Provider for SQL Server
Error Description:[DBMSSOCN]General network error. Check your network documentation.
My guess is that the things are looking for Server X and now they're on Server Y. Problem is, that when I try to edit the properties of the 'little line'...that error pops up...and then the window that comes up with the tabs across the top of it that lets me enter the SQL statement disappears right away and I can't make the changes?!?
Other question:
The SQL Server is now on a machine that's like 3000 miles away. Right now I use pcAnyWhere to log into it and use the SQL Enterprise Manager there.
Well, I've got SQL Server installed on this machine here...surely there is a way to have this SQL Enterprise Manager here connect to the remote SQL Server so I can play with it that way instead of the pcanywhere mess...right? Seems logical....
I'm making a system to data acquisition (production) and need more (3) tabels with a heavy load of data.
3 tabels will contain approximately 20-50 milion rows. Every day I need to add 80000 rows to these tabels. Will I get problems with system-performance with such a configuration? Ofcourse the system will contain index in the database and 2 fast 1 Ghz intel CPU. I isn't possible for me to seperate or archive theese tabel, because of researc-functionality.
I am still fairly new to Sql Server 2008 R2 (express) , but am enjoying exploring it.
I have several databases up and running and now a large number of users in each.
But I notice whenever I write a stored procedure I have to go in and add each user to give them permission to exec it. When the user numbers are low its not a problem but I now have over 20 users on 1 database and its becoming tiresome.
I have heard of Active Directory on Windows Server but my database is installed on windows xp professional PC. Its running well and we don't have a budget to change it.
I've been searching the internet to see if there is some way I can create a group within sql server give the group all the necessary permissions/ privileges and then add the users to that group thereafter...
Do DBAs need OS Administrator rights to Manage SQL Server? I suspect the answer is no, but, the DBAs tell me that they cannot do their jobs without OS admin rights.
Can someone point me to documentation detailing what OS level rights are needed by SQL Server DBAs?
Hello, I think now MS SQL 2005 support packaging database object into schemas which may be granted access by any of the db users, while SQL 2000 only we could use the database creator user instead of schema. my case is i am working in a system with more than one module, e.g. HR + TaskManagemt. Both HR and TaskManagement objects are in the same database, and there are some common objects. I want to isolate the HR objects from the TaskManagemt objects, so i can package any module separated from the other, suppose i want to buy only the HR module, so that i want only to exctract the HR Object + the common objects but not the TaskManagement objects. So how can i accomplish such operations using SQL 2005 schemas AND using SQL 2000 users. P.S. i have two servers one with 2000 and the other with 2005, so i want to find solutions for both 2000 and 2005 Thanks in advance
Does anyone know how to reserve a number of concurrent user licenses /per server logins in MSSQL 2000? I have a situation where I have more users than I have licenses for an enterprise SQL application and would like to make sure that a certain group of users always has access to the system. Individuals who only need inquiry access should only be allowed to login if there are licences available beyond the core group of users. Any Ideas? Thanks.
I am in need of a utility (stored procedure, third party app, etc)that will help streamline the process of managing and auditing objectpermissions, users and roles on multiple sql server 2000 instanceswith multiple databases on each instance. That's a quick overview ofwhat I need, do I need to be more specific?Thanks.
Hello our organization has never had any problems getting users to connect to our SQL servers but we have grown a lot over the past year or two. Does SQL Server actually block connections if they go over the license limit? I don't have access to the servers to see the model used but I have been asked to look into this. I couldn't find any information on this so I decided to ask you guys. Thanks in advance.
Suppose someone has to work on a lot of different SQL Server Databases which have got a lot of Tables and Queries / Views inside them.
After a period of time, it becomes very difficult to remember exactly what kind of columns are present within a given Table and View.
Any method by which one can keep a systematic list of all the Tables and Views that are present within a SQL Server Database, along with the columns that are present within them.
Are there any Add-on products or services etc. available in making this type of work systematic?
Currently I add comments to each queries inside SQL Server to remind me of what this query is doing, but this method is not great.
We are currently running sql 2000 and are moving our database onto sql 2005 running on a different box.
We have managed to move the entire database, with users however the users permissions on specific tables/views/stored procedures have not been transferred, does anyone know a way of transferring user permissions rather then doing them all by hand?
The system is a large (over 500 table/views/stored procedures) and a very active one and therefore downtime is not optional.
Based on our database infrastructure, we need to secure our SQL databases. The security issue concerns on allowing a limited number of Domain Admin users to access the SQL databases. We tried certain ways, based on the documents in the Microsoft web site, but we couldn€™t reach to the point of preventing the Domain Admin users accessing the SQL databases.