Is there such a thing as a Production DBA in the SQL Server world or is this an outdated concept? Is there a market for people who specialize in database administration as distinct from software development or general network admin? I believe there are such people in the Oracle world, is the SQL Server world different in this regard? Can anyone give me suggestions about how to go about filling such a position?
I am a New York City area employer seeking to fill a position that I think would be ideal for a DBA with 3-5 years of experience in a production environment. The salary would be somewhere between $50K and $60K.
The position involves administering a SQL Server cluster and SAN running our core business application, plus several ancillary SQL Server installations. The application that we are implementing is a third-party product, so no real development is being done at our site. It is, however, fairly complex and requires customization and we do have significant reporting and EDI requirements, so strong T-SQL skills are required.
We are a medium-sized operation, with 900 employees and an eight person IT Dept; the organization’s main focus is insurance not IT, so candidates with a lot of experience might not find it challenging enough, but I think it would be an excellent opportunity for a candidate who might be stuck in the back of a large IT Dept. who wants to move up to a more visible position in a smaller organization.
I would think that there would be a lot of people in this category and, indeed, we have received a lot of resumes, but few of them are from the type of candidate that I had in mind. Most of the resumes are from people whose main focus is development or, if they have had experience in a production environment, have had 10+ years and are seeking salaries way beyond what we can pay. As for the former, I would not automatically reject someone whose prior experience was as a developer—and these skills would certainly be useful to us--I would just be worried that they wouldn’t be happy if they weren’t spending all of their time developing.
I have a challenge for all DBAs. I am getting INCONSISTENT TIMINGS for Querry Results from a SQL Server 2000 Standard Edition on a HP Proliant 2 CPU Server with 4 GB RAM and SCSI DrivAFAe. Our Database is 72 million records and have 8 columns. Most of them are indexed, which are used in the “Where…� clause. In addition to independent indexes, we also have a covering index for 3 most frequently searched fields. My challenge is that out of the 7000 odd queries that hit the server with various search conditions in a Week, 5% of the queries return result in less than a minute. The same query at a different Time or with a different Value, returns results inconsistently. For e.g. searching FirstName = “Anna�; LastName = “Williams� returns result in 0.01 sec. Searching for FirstName “Benjamin�; LastName = “Watson� returns in 5 minutes. Any kind of help is welcome and will be highly appreciated. - Santy san.rely@gmail.comNote: Edited to fix white on white font.
We have an audit happening on our DB environments. All are SQL2008R2. One of the risk highlighed is DBAs are also part of 'Administrators' group on the server. The DBAs having sysadmin (ie full control)on SQL server is not a risk but DBAs included in 'Administators' group is termed as risk.
My question is do the DBAs really need to be Administrator on the box apart from Sysadmins??. If yes,What are the scenarios in which DBA group also need to be an administrator on the box to manage daily admin activities.Â
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?
I have been working as Sybase DBA for 5+ years, and I would very much like to add MS SQL Server to my resume. Given the common roots of the two RDBMS, it seems that the learning curve would not be as sharp as if I were going to learn Oracle or DB2. Can anyone out there know of any books that are geared toward learning MS SQL Server from a Sybase DBAs perspective?
I am a Windows Sysadmin (Active Directory, infrastructure, etc) with light knowledge of SQL 2005. I can set up the database cluster on a shared storage device, I know how to get the heartbeat, do simple backups, etc.
My question pertains to disaster recovery. Right now, we use a product called DoubleTake to copy our database over and 'assume' the identity of the failed SQL server. There are two problems with this -- cost of the license of DoubleTake, and additionally, is it the best method?
I have read before, that you don't need to be a DBA to set up a DR scenario for SQL. My goal really is to have two databases -- one in our production location, and one in a DR location that is pretty much cold (for licensing issues).
If our production database should go down, then it would fail over to the DR site.
What is involved in doing this, what type of steps are required, do you NEED a DBA to manage this, or can a sysadmin (such as myself) take care of it? Also, is it worth having DoubleTake to do this job, and does it do a better or worse job, are there limitations, etc.
Thank you for any replies you can give, and please keep in mind that I'm far from a DBA .
How easy it is to deploy a solution that uses SQL Express on Development, but a MS SQL database on the production server (host)I am using the membership provider of ASP.net 2.0 Many thanks.
I just deleted a stored procedure in order to replace it with a corrected version (DotNetNuke). Now I had the following problem : When I try to create the SP with the following :
IF EXISTS ( SELECT * FROM sysobjects WHERE id = object_id(N'{databaseOwner}{objectQualifier}GetUserRolesByUsername') AND OBJECTPROPERTY(id, N'IsProcedure') = 1) DROP PROCEDURE {databaseOwner}{objectQualifier}GetUserRolesByUsername GO
IF @UserName Is Null BEGIN SELECTR.*, U.DisplayName As FullName, UR.UserRoleID, UR.UserID, UR.EffectiveDate, UR.ExpiryDate, UR.IsTrialUsed FROM{databaseOwner}{objectQualifier}UserRoles UR INNER JOIN {databaseOwner}{objectQualifier}Users U ON UR.UserID = U.UserID INNER JOIN {databaseOwner}{objectQualifier}Roles R ON R.RoleID = UR.RoleID WHERE R.PortalId = @PortalId AND (R.Rolename = @Rolename or @RoleName is NULL) END ELSE BEGIN IF @RoleName Is NULL BEGIN SELECTR.*, U.DisplayName As FullName, UR.UserRoleID, UR.UserID, UR.EffectiveDate, UR.ExpiryDate, UR.IsTrialUsed FROM{databaseOwner}{objectQualifier}UserRoles UR INNER JOIN {databaseOwner}{objectQualifier}Users U ON UR.UserID = U.UserID INNER JOIN {databaseOwner}{objectQualifier}Roles R ON R.RoleID = UR.RoleID WHERE R.PortalId = @PortalId AND (U.Username = @Username or @Username is NULL) END ELSE BEGIN SELECTR.*, U.DisplayName As FullName, UR.UserRoleID, UR.UserID, UR.EffectiveDate, UR.ExpiryDate, UR.IsTrialUsed FROM{databaseOwner}{objectQualifier}UserRoles UR INNER JOIN {databaseOwner}{objectQualifier}Users U ON UR.UserID = U.UserID INNER JOIN {databaseOwner}{objectQualifier}Roles R ON R.RoleID = UR.RoleID WHERE R.PortalId = @PortalId AND (R.Rolename = @Rolename or @RoleName is NULL) AND (U.Username = @Username or @Username is NULL) END END GO
I get the following error :
"Syntax error, permission violation, or other nonspecific error"
We have developed a project with many SSIS packages. Now we are in a stage where we are deploying this into production.
The operaitons team has asked us what are the things they need to known and do to make sure that the production system of SSIS keeps running.
Can you help me in comming up with a detailed list which I can give to the operations/admin folks so that they can ensure that this project keeps running?
I must release a new Db on 4/1 into an isolated small network (pier workgroup) and my choices are MSDE or Express. I'm new to both (MSDE yesterday, Express today). I am familiar with SQL Server and prefer using the tools with Express, but is it stable enough to use in this type of production environment?
Everything works well in development mode when I click on Preview, the report is shown as I want.
But In Production this is how my report is shown
My Report
Public
Private
Total
Category
SubCategory
x
x
x
SubCategory
x
x
x
Total
x
x
X
I don€™t understand why the Total column returns false for the InScope("SubCategory")," statement and that only when my report is deployed on the production server.
Hi all, I have a asp .net 1.1 application running on the intranet which uses SQL Server 2000. The application is in production and everytime I want to do some changes, i do the changes on my development machine then I copy the application dll on the server. The problem is that I'm using Stored Procedures for all my Select, Insert and Delete statements. These stored procedures are live on the server so I can't do the modifications locally and test them then copy to the server.
How can I do modifications without affecting the production server and the users ??? thanks.
I will be hosting my website in the next few months and doing more testing and I was having trouble finding a place to host the site that allows enough space for my sqlserver2005 database. I am estimating that the database will be around 40-50GB. Most hosting companies only give about 500MB for the database. Does anyone know of a company that provides more space? Also, is SQL Express production ready, or is it just for developing applications? If it is production ready, is there any "major" performace impact in using it over the full version. The reason I am asking is because hosting companies only give 500MB for a database, but alot more space for the web page. If I can put the SQLExpress file in the App_Data folder, then I will have more space. Does this even sound like it will work? Opinions are appreciated!
ok ok, stop laughing. for real, is there any programatic way of doing this? whom ever created this database i inherited (SQL 2000) created the LDF and DATA files on the same drive and in the same folder for that matter. just trying to do a little disaster magament.
we have a situation where modifications to the stored procs and views keep happening in the development databse environ while there is a live production database also up and running.
periodically we need to ensure that the development and the production are in synch where all changes made to dev are transferred to prod. however the entire prod database obviously cannot be overwritten as it contains production data. therefore what we need to do is to transfer all SPs and Views from the development to prodn. ( we do not prefer incremental transfers as there are many SPs and views and we can never really be sure that all changes have been transferred )
the obvious way is to script out all SPs and views in dev and run the scripts in prodn. but what we encountered was the enterprise manager does not script out the objects in heirarchical sequence - ie parent objects first and then the objects that refer the parent objects. this leads to errors when running the scripts as the objects required for the creation of a SP, say another SP run from within that SP , may not have been generated by then as the "contained" SP is lower in the alphabetical order in which SQL server scripted out the objects.
finally we had to look at each and every error and manually set the process right.
moreover in the way we did things the "sysdepends" table got all screwed up and therefore we can no longer depend on enterprise manager to show dependencies within the database.
is there any elegant way of going about this ? we also tried transfer manager in DTS but it also gave the same error. moreover can the sysdepends table be rebuilt from scratch ?
I am interested in hearing from those who are using SQL7 in production. Please include size of database, number of users, implementation date and experiences to date - good bad or indifferent. Thank-you, Leo
This feels like a silly question, but I`m going to ask it anyway...
I have limited SQL Server experience, but have run into a wall with a client`s Web/Access combination. I need to upgrade to SQL Server. I have Beta3 installed on a development box and am very happy with it. Is anyone running this thing in a production environment? This isn`t going to be experience huge loads, so I`m tempted. Tell me if I`m crazy for wanting to try it.
Sould one has a seperated environment for production and test system? How do you do it on a same server? Install two instance? How do you seperate test DBs from the production DBs? Please advise...Thank you
I have a brand new database server with system databases. I need to copy like four production database from another server to this new server. Can i do restore of the last production backups and restore them on the new server without creating the empty databases on the new server.If any one has better approach i will appreciate
I have a database db1 on server1 and server2.The Db On server1 is a production db and the Db on server2 is a staging Db.All the new data will be coming into production Db.And i wanted to update the data and database structures on staging Db from production Db on weekly basis.So how can I reflect the data and datastructures on my staging Db from my production Db.
Was wondering, when performance changes have been made to existing code and deployed to a production environment, should anything be done regarding clearing old cache?
Is there a risk of the new code picking up cold or wrong cached query plans etc?
I know you can't clear the cache for the full system as it will affect everything else. But are the ways to target the changes? I.E run the new code with an OPTION (RECOMPILE) few times to build up new clean plans for it to use?
Or will the update stats see it is using bad plans and then start creating new clean ones over time?
This is probably an easy solution for some of you seasoned DBA Vets but here is my problem.
I have to take production data and scramble certain sensitive columns such as SSN, DOB, Address, First Name so that our Management team can use it as demo material. Is there a quick solution to this issue?
1.First issue The port number already allocated was 2059. We have changed that into the default port 1433 in the node. Now we are able to connect the node from the client application. But we are not able to see the configuration manager in any of the environment now.
2. 2nd issue Cluster Environment
Error while executing the Package The connection details are not loaded in the connection manager tag
OK, I'm troubleshooting a performance issue on one of our production servers, but I really can't t-shoot and tweak in real-time, so I took a snapshot of "a day in the life of" my production server using the profiler.
I want to run the sql commands I collected on another server I set up identical to production, and play around there.
Does anyone know of a good tool to "replay" those captured commands onot another server?
I have production server 2000. The server gets disconnected sometime by itself and sometime it is working fine.Sometimes it even doesn't get restarted. Is there any problem with service packs and some performance issues. Can you SQL guru give me best suggestion and how should i proceed.
I'm totally new to SQL. I have a SQL 2005 server with 3 sets of mirrors - 1 for the OS, 1 for the logs and 1 for the DB. SQL had already been installed and DB's put into production before I knew the logs and DB's were all on 1 mirrored set. I need to move the logs to their own drive. How do I accomplish this?
Hello faculties,We've a production database that is being used by one of our clientsas a backend for his website. The database size is around 1GB.Recently we added some tables to our local database which is areplica of the production database. Now we need to apply the samechanges at the production one aslo.I've no clue about what steps should i implement.Please guide me!Thanks in advanceDebian*** Sent via Developersdex http://www.developersdex.com ***
