This may be an intuitively obvious question, and if so, I apologize.
Speaking in terms of best practices here, what is the preferred method for allowing developers to work with databases in SQL Server? If they use Management Studio, then they have access to tools for perhaps messing with other databases, etc. that they should not (assuming it is not correctly secured). Likewise with Enterprise Manager. I can see where they would use Query Analyzer, but these two are now combined in Management Studio.
I'm just inquiring into how other DBA's do this. I realize there are DBA's that are developers and vice-versa, but what if there is a clear line of distinction and you want to keep the tools used in these roles separate?
Login failed for user 'TOSHIBA-USERASPNET' I know that the file persmission for the web application have to include aspnet, so i keep resetting the folder permission for aspnet in file manager, but the login failed keeps coming back every day or two problem is after working with VS05 Pro, SQL Server Management Studio CTP, somehow the aspnet persmission get changed, use alot of sqldatasource wizards and often there is a conflict/hang between the datasource wizard and the need to have the mdf in a dettached state within VS server explorer, not sure but the procedure to fix this seems to be to reboot, detach and re-attach the mdf in the Sql server Studio tool, re-apply the aspnet file permission on the web app folders (wonder should i be doing this in IIS instead), make sure the mdf within server explorer is detached, the it works anyway, getting real tired of the resulting delays and design time derailment, clues greatly appreciated, thanks sometimes i can use View in Browser when in VS05 form view and i wont get the aspnet folder permission error and other times i do. last thing, is it a bad idea to give aspnet full permission for the entire web applicaiton??
Hi,I have just started a business and I was wondering if I could get someadvice about product selection. I am currently buiding my websiteusing asp.net connecting to sql server database.My question: Am I only required to purchase a SQL Server DevelopersLicence? I won't be hosting the site so I think this is correct butthought I should check.Cheers,Jack
I just bought a copy of SQL Server 2000 (with service pack 3a) that Iintended to install and run on XP Pro. My concern is that the requirementslist on the box do not include XP or XP Pro. Will SQL Server 2000 developeredition run on XP Pro?
I have downloaded SQLServer2005SP2-KB921896-x86-ENU.exe and attempted to update to SP2 with no success.
SQL Server 2005 Developers Edition is installed on my computer as part of a Visual Studio 2005 installation.
When I try to run this package under my admin account, I get through the Feature Selection (selecting everything) to Authentication.
When I press the Test button or the Next button, I get "Your account information could not be verified. Press Ok to return to Authentication Mode screen to determine the reason for failure. For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator."
The Authentication screen shows "Database Services, MSSQLSERVER, Windows, domainusername, Service Failed to Start"
I am a novice SQL Server user, Clearly I am floundering! Any observations, advice, or suggestions would be greatly appreciated.
I have a problem. I am using the developers version of SQL Server Enterprise edition.
I am trying to run a command in MS command prompt:
Aspnet_regsql -E -S localhost -ssadd -sstype p
After I execute this command, I receive a Name Pipe error that under the default settings, SQL Server doesn't allow remote connections. I took some steps to try to resolve the problem:
1) I googled the interrnet to see if there was any one else who ran into the same problem and if there was a quick resolution.
2) I check SQL Server Books on line about SQL server configuration manager and how to enable remote connections using Name Pipes and TCP/IP.
3) I used C:WINDOWSsystem32cliconfg.exe to enable Name Pipes and TCPIP to be enable on the client.
4) I enabled SQl Server Browser to help me with my problem
5) I stopped the Database engine, enable local and remote connections using Name pipes and TCP/IP,then I restarted the database engine along with SQl server Agent.
6) I did check SQl Server error logs to see what port it was listening on , but I thought that SQl Server was suppose to listen on port 1433 by default, and Name pipes /SQL/query.
7)I have check the error logs to see what port that SQL Server was listening to and trying to use the port number in the client config utility. I am still getting the same error.
8) I tried to remove name pipes in the SQL Server Surface Manager and allow local and remote connections using only TCP/IP. I still get the same error. I did stop and restarted the Database Engine.
What steps have I not taken , and what should I do to correct this problem?
The installation SQL 2008 R2 Management Tools on a Windows 7 workstation fails with the error, The specified account already exists.
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
I am running SQL Server 2005 x64 Enterprise under Windows 2003 x64 Enterprise. My current backup strategy uses T-SQL jobs run by SQL Agent (writes out *.bak files) and then I have an Integration Services job that copies the *.bak files to our NAS device. I have performed a restore without issue. The jobs are all automated every four hours via SQL Agent. Is this a sound strategy or are there additional benefits to using 3rd party tools? If so, what are the advantages and which tool provides them?
Is there - apart from the notorious RESTORE HEADERONLY - an tool which is able to tell which SQL Server version created a specific BAK file? I'm looking for a tool that can be used w/o an available/running SQL Server installation.
Alternatively, is there any documentation about what is read with RESTORE HEADERONLY so I could write a tool myself?
Where would I find the version "bytes" in a BAK file?
I'm really new to MSDE so I just want to know...Is SQL Server 2000 a prerequisite for MSDE particularly for developers? If yes, then is it(SQL Server 2000) a prerequisite for clients?
The thing is, I can't find a tool where I can create databases after installing MSDE...the only way I can think of is also installing SQL Server 2000 and create the database from there...
Hi, I've just released Nautilus v1.0.6. I would apreciatte your opinion and comments. With Nautilus you can: -search tables without tipying the exact name. -browse records, filter and locate records -"Pivot" records to see it's related records (folowing the Foreign keys). -Generate scripts: create table, insert into, delete, update. -Build dynamic diagrams.
OMNI GROUPJoin Bytes!T-SQL/ CONTRACT TO PERM/ ATLANTAI'm looking for 1-2 TSQL developers for a 4 month contract to hirerole in Atlanta, GA. Ideally the candidate would be local or regional and aUS Citizen with 2-4 years of Microsoft TSQL development experience.Salary in the $55,000--$60,000 or so. annual range. Contract rate would beApproximately $36 hr W2 or 39hr 1099. One is responsible for their ownexpenses.Once perm, the company offers full benefits.If interested and qualified, answer the six questions below. EmailanswersWITH a resume to: Join Bytes!1. TSQL experience-------------------yrs2. MS SQL experience---------------yrs3. OO Languages----------------------4. Citizenship Status------------------5. Availability--------------------------6. Contract Rate ---------------pr hr..
New to SQL so please be patient. I'd like to give my developers "See All/Do Nothing" rights to my production server. I want them be able to see everyting that I do, as SA, but not be able to change anything. Is this possible?
I will have a group of developers creating objects in a database. Currently they all create them with the SA account. I would like to have them mapped to the dbo or some method that when they create objects all objects are dbo.object name and not h1fed99.object name. Is there a good methor or practice to handle this
I'm currently trying to obtain an aggregate function from a table to provide a cumulative monthly value. I would like to create a view to obtian this from the underlying table i.e month=1 ,month=1,2 , month=1,2,3 Etc.
Always looking for people who are strong with microsoft technology for new oppurtunities in the Seattle area. If you are good, we can help you find your ideal next position.
I am looking for mid to senior level SQL developers for some sweet companies here in Seattle. A chance to work in a dynamic envirnoment with bleeding edge Microsoft technologies. Are you good? then we can help.
I am looking for strong SQL developers and/or DBA's for some really sweet companies here in Seattle. Anyone interested that is good and wants to hear about new oppurtunities? I would love to help you out.
Were looking from some feedback, thoughts, comments, suggestions on a permissions issue in our SQL Server 2005 environment. We have a Development (stand-alone server) and Production (activepassive cluster). Both running SP2. We're looking for the best way to manage permissions for the developers without giving them dbo privileges.
As background information, here's a note / response from a developer outlining the permission they need.
-----------------------------------------
"Our team needs enough permissions on DB database to:
Create and modify DB object such as tables, stored procedures, keys, triggers, views, ...
Be able to execute stored procedures and other basic DB objects
One of the issue I had when working on DatabaseA which was never resolved was that I could create tables, but had no rights to modify them once created.
I could modify them via scripts, but not via graphical interface which is a pain.
I think we should have full permissions to dev DB other than to drop DB, and modify system DB settings.
So that we can work within the created DB shell completely."
-----------------------------------------
Previous to supporting the current SQL Server 2005 environment, the developersapp owners had db_owner for their databases. Definitely not a best practice as with 2005 db_owner is ablke to delete databases. Moving away from this, we thought we would scale them back and only grant them the following database roles:
db_datareader
db_datawriter
db_ddladmin
With these roles, they were able to create the tables, views, stored procedures, etc...... but problems arose when they tried to modify the objects they created as well as execute stored procedures. It's going to be a pain to grant permissions on each stored procedure. More of a mystery is allowing them to make design changes within Studio Manager. Given they can already do this using scripts but not the GUI.
So there is an issue with using GUI tools to design the tables.
Here's a thread we found that tries to explain the reason why they can't use the GUI to make design changes.
Even if you have CREATE TABLE permission, there are limitations to the modifications you can make. Remember, as you modify an existing table or design a new one, your work can induce attendant modifications in other tables. For example, if you change the data type of a foreign-key column, the corresponding column in the primary-key table will be automatically modified by the Visual Database Tools. If you do not own the primary-key table, and you are not logged in as the system administrator, database owner, or a user that is a member of the db_owner role, your modification will fail.
When we created the accounts, we assigned the default schema to be 'dbo'. This was thought to simplify administration of the objects. In SQL Server 2000, this was a best practice. Now, in SQL Server 2005, they changed everything with the user schema separation.
So we have a developer (devuser) - created with default schema (dbo). Any object that are being created are owned by dbo. (ie... dbo.table1, dbo.storedproc1, etc..) So dbo owns the objects, not the user.
Does anyone have any ideas? Do we create a new schema and assign permissions? Do we create a new fixed database role for the developers? I'm curious as to how others are assigning permissions to developers on development and production servers.
What is the best practice in managing an SSIS development with multiple developers.
For example, we have 2 guys that will be developing various SSIS packages for a common data warehouse. We are most likely going to divide up the unit of work by the tables that need to get loaded. So, one guy will develop packages to load tables 1 thru 5 and the other guy will develop packages to load tables 6 thru 10.
Should each person work within his own project? (Not sure what a difference between a solution and a project is, so I may be thinking of a solution.) If so, can multiple people open the same project? I don't think you can.
I'm very new to SSIS and this would be the first time I'm doing something like this. I haven't even deployed a package to the server yet so I'm not even sure what implications/consideration I have before I take on this development effort I'm about to.
Is it possible to use SQL express to create a web application that is developed by more than one user? It seems to be registered on the <machinename>/SQLEXPRESS but the ASP.NET tool in visual studio seems to always want to create a sql express version in its app_data folder.
How can i set up a database such that 2 or more people can use that for developing the application. No doubt that SQL express with be suitable eventually, but initially we need to access the same database for development, but be on multiple machines. Can this be done, if so how?
I have problems with the concept of user-defined messages. I'm migrating from sybase ase to sql2005 and found out that there is only one global pool of messages. Do you give every project on this server a dedicated range of error-numbers?
Another problem: only the sysadmin oder serveradmin can call sp_addmessage. In my environment the developers own their databases and used to be able to create their own messages.
Now I try to let the developers call sp_addmessage by calling a "wrapper-procedure" which gets the needed rights.
create procedure sp__addmessage(@msgnum int, @severity smallint, @msgtext nvarchar(510), @lang sysname )WITH execute as OWNERASselect 'I am ' + suser_name(), user_name()exec sp_addmessage @msgnum, @severity, @msgtext, @lang gogrant execute sp__admessage to testusergo
When executing it as normal user (without sysadmin/serveradmin-roles) the output is: I am sa dboMsg 15247, Level 16, State 1, Procedure sp_addmessage, Line 18User does not have permission to perform this action.
Isn't it strange? Do you have a different idea how users/developers can create messages?
I like to get a feedback from other DBA's out there, I have a user with a consultant that need's Enterprise Manager installed on the user's desktop in order for them to develop code for the user.
Is the above a good reason to give out to the user the Enterprise Manager tools?
Please give me what is acceptable tools for the user/consultan.
since Sqlserver 7.0 looked so easy to our developers, they would like to perform development and administator tasks. Our environment will begin with 3 development groups, each with about 1-4 developers per group. We're might reach about 10-15 dbs with in a year. Most of the databases will be under 1 Gig(may be under 500 MB) and may be couple 2 Gig Dbs. We're not sure how many more databases we'll have.
