Where should SQL developers be working?

S

*SynergyX*

Expert Member
Joined
Sep 30, 2009
Messages
2,943
Reaction score
528
Should SQL developers be developing on their local machines(i.e using tools installed on their local machines to connect to dev,qa,prod instances) or through RDP sessions on Virtual machines?
 
I prefer tools on machine and connect to run on remote or local vms.. but thats just me (not a sql dev tho). I like it this way as then i can keep the IDE/Tools up-to-date and run on a plethora of versions for testing.
 
RDP sessions are frustrating as ****, especially when users are limited and you have more than 1 dba/developer

There should be no reason for you not to connect through the network with tools installed on your machine going to the server
 
envo said:
RDP sessions are frustrating as ****, especially when users are limited and you have more than 1 dba/developer

There should be no reason for you not to connect through the network with tools installed on your machine going to the server
Click to expand...

Did some years connecting via Citrix to an RDP session in the USA. Kill me now.
 
There isn't necessarily a better option, or one is better than an another.

Here's my take on it:
RDP-VM Pros:
Can keep sensitive data secure (if setup properly) such as client PCI data.
You won't lose your session if your local PC/laptop crashes.
Resources management is handled by the server administrators, no need to worry about the PC/laptop spec.

RDP-VM's Cons:
Sluggish IDE response and feel to it. (the UI is streamed from the RD, my personal gripe)
Increased cost, you still need a server to host the RDP sessions and the SQL session.

Local Pros:
Better IDE responsiveness.
Multi monitor support is way better.
Doesn't necessary need a beefy PC/laptop, query processing is handled by the SQL server session anyway.

Local Cons:
If you PC/laptop crashed you might lose work that's in the query window at that time.
Your data query can be interrupted by network or power failures.
You could possibly export sensitive data from the database.

Personally I enjoy using the Local installed instance of my IDE, I like the responsiveness of the UI
 
SQL development should only happen on a local (sanitised) backup of production.

I used to work through RDP though, its not idea for various reasons but worked well for many other reasons.
 
All development to take place on local machines, then deployed to test environment,tested 100% then deployed to production environment at my company and every company that I have worked at.
 
I think:
1. Dev + Testing local machines as long as your data is sanitized and you have a fully functional replication of Prod.

2. Production - RDP only, you should not be deving anywhere near prod, so you should not need any connection to it via local machine, way to easy to extract data.


I personally prefer local machines, its always faster and more coherent than having to RDP to servers, especially if they located elsewhere. You have your own machine all set up nicely for efficiency with shortcuts/required programs/etc.

I've done all of them.
1. Local machines within our own network, nice easy happy.
2. RDP from Mauritius to SA with 400ms, develop on servers - Death to all
3. Mixture of local network development and RDP, not bad, but if i connect to my local network, i cannot connect to the other RDP and vice versa because each requires their own VPN connection, drives you mad aswell if you need to quickly switch between environments.
 
Last edited:
Im still amazed to find people that still think its ok for developers to have access to production servers. If someone has to ask how its possible to to operate without dev access to production, then they are in the wrong line of work. This is something so fundamental, that if you dont know why its a bad idea, then you you shouldnt even be allowed near a dev machine. :)
 
zippy said:
Im still amazed to find people that still think its ok for developers to have access to production servers. If someone has to ask how its possible to to operate without dev access to production, then they are in the wrong line of work. This is something so fundamental, that if you dont know why its a bad idea, then you you shouldnt even be allowed near a dev machine. :)
Click to expand...

When I started at my previous job we were a small team of 3 devs, ranging from intermediate to (very)junior. Everyone had full admin rights for at least a year on the production server, including all databases. Boy, it was a wild ride!
 
zippy said:
Im still amazed to find people that still think its ok for developers to have access to production servers. If someone has to ask how its possible to to operate without dev access to production, then they are in the wrong line of work. This is something so fundamental, that if you dont know why its a bad idea, then you you shouldnt even be allowed near a dev machine. :)
Click to expand...

Why? I have full access to the live environment, all live servers, all live databases.They know that its unlikely I will **** up.Its not safe though and that schit wouldnt fly at a financial company.
 
zippy said:
Im still amazed to find people that still think its ok for developers to have access to production servers. If someone has to ask how its possible to to operate without dev access to production, then they are in the wrong line of work. This is something so fundamental, that if you dont know why its a bad idea, then you you shouldnt even be allowed near a dev machine. :)
Click to expand...

Read access only on Prod servers and only for senior devs. And only if it is really necessary for extreme edge cases that can not be recreated in the dev environment.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X