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 |
|
kid_on_the_block
Posting Yak Master
172 Posts |
 Posted - 2006-05-10 : 00:14:27
|
| Hi Heard a lot of people talk abt production & development environment what all do they mean .....Does supporting a production environment mean that its only administration of the box & does Development mean codint the T SQL statments Someone please help & clarify this doubt....Thanks |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-10 : 00:56:15
|
production = live environment, mission critical, depending on policy = 24x7 up and running, highly available aka don't mess around with this environment if you love your job  development = offline environment where you do all the development, testing and risk analysis etc, aka playground in some companies i've been with, development is like production to the developers, still same administrative tasks but less rigorous and a bit more lenient--------------------keeping it simple... |
 |
|
|
kid_on_the_block
Posting Yak Master
172 Posts |
Posted - 2006-05-10 : 00:59:22
|
| I mean as a DBA , what does it mean stating that I have exp with the production environment & having exp with the development environment......Which of them is critical ...I am only into Database Administration .... Dont knw the TSQL , can I be a production DBA ??? What would me role be then .... |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-10 : 01:07:16
|
| both are critical, if you produce poor db design and admin jobs, you pass that up to productionbut to say you're a production dba means you need to support the servers real time mode and need to monitor it's performance and get daily statistics and make sure that everything is running as it should be, able to handle daily stress, able to respond to a concern before it becomes an issue, provide more than 1 solution to a problem and able to decide which to take, etc...in short, production dba are more stressed out compared to development because development DBAs have the luxury of time and resources at hand, while production DBAs are always alert even when sleeping (for 24x7 support, on call duties etc), thank goodness i'm not a production DBA anymore--------------------keeping it simple... |
|
|
|
druer
Constraint Violating Yak Guru
314 Posts |
Posted - 2006-05-10 : 16:42:43
|
| Adding on to Jen's comments ....In a development you can freely go about playing with queries, creating new jobs and running them to test whenever you want, adding indexes at will etc.In the production environment you have to realize that every command that you run will be affecting the performance of everyone else. So instead of running the commands against the production server you run them against a development server to verify that they will work. Then you will take the TSQL for those things and schedule them to run as jobs after hours so that they don't impact the production system and thus end users.You would take sample code to resolve peoples issues from a forum like this and test it in the development environment, and not in the production environment. Of course when it comes time for your performance review you can purposely rebuild some indexes on your major tables so that the system will slow down and the boss will call screaming. You can say "Hang on boss let me get in and see what is going on ..." Then you call them back about 2 minutes later after the index finished being rebuilt and dragging the system to a halt and say "I found the problem and fixed it." If you do that a few times near review they think to themselves "I really need this person." Of course it could backfire and they could think "I'm tired of these problems maybe I need a new DBA." But no risk ---- no reward. :)Hope it helps,DaltonBlessings aren't so much a matter of "if they come" but "are you noticing them." |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-05-10 : 17:18:02
|
| A production environment will have a sla and you have to provide features to support that - i.e. backups/restore strategies, standby systems, dr sites, failover systems. You will need to monitor what's going on to spot problems that are going to happen and put things in place to be alerted if there is a problem. In particular you should never run out of space for any object.If it goes down (or just degrades) it affects the business ability to work and a lot of people will probably get upset.You would also be expected to know about integration test and system test systems and have a method of migrating releases through them and also to detact anything that gets onto the production system without going through the process.For a dev system it's more about providing a platform for people to work. If it dies then development just gets delayed - some people might get upset but developers will probably happily ajourn to the pub. It will be expected to go down and run out of space as developers do stupid things. You will be expected to condecendingly point out their mistake rather than stop them making it. You can even tell developers it's up to them to keep backups of there own data.>> can I be a production DBADepends on the company. There is usually a need for someone who just takes care of admin type tasks but isn't expected to troubleshoot or be proactive. Look for something like a junior production dba role.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
|
|
|
|
|
Difference between production & developement