July 10, 2008 at 6:28 am
A long time ago, I read that installing your IDE on your database server and doing development directly from this database server was a very bad thing to do, but can't easily find any articles to support that...
If it's your desktop, that's one thing... But should you ever install, lets say any Visual Studio IDE and do development directly on a shared database server?
No "opinions" please. I only want recommendations and facts (links are good) to support the recommendations.
Thanks.
July 11, 2008 at 6:53 am
How can there be no replies on this?
OK, I'll take opinions... What's good about developing application (using say, Microsoft Visual Studio .Net) directly on your shared SQL Server database? What's bad about it?
Anyone?
July 11, 2008 at 9:28 am
Ok, now that you're taking opinions..
My opinion would be not to do it. Whether it's a production or development SQL2K DB server all you want running on that machine is the SQL service. For some quick reasons I'd say:
a) Visual Studio is a resource-hungry beast (that I couldn't live without). To narrow down memory leaks or pegged processor need to know if it's DB server or local machine.
b) Need to simulate production environment as close as possible in development. Let the data packets roam over the network pathways instead of a quick hop through a local machine. Let network user permissions come out to play.
c) Ever completely hung your computer (while using an API for example)? Happened more back in VB6 days but a thoughtless moment or 1 instead of 0 can take the box down. You mentioned it's a shared server. You've now taken everyone down. Downtime - whether development environment or production environment - costs the company money.
d) All I've ever heard says don't do it. I put that right up there with not using cursors and declaring meaningfully named variables.
I guess one other way to look at it would be "What advantages could I possibly gain by installing the IDE on the same machine?". (Aside from not needing to buy an extra computer)
July 14, 2008 at 6:31 am
Mike Nuessler (7/11/2008)
Ok, now that you're taking opinions...d) All I've ever heard says don't do it...
Opinions are good, and I totally agree with 100% of what you stated. Actually, the things you mentioned are all very logical and well known - but I can't find any facts anywhere that would let me do what I want, which is to send an e-mail telling one of our other senior developers that this is a bad idea, and including a link to some facts that support why.
The last thing I want to do is look like I'm just complaining about something because I like complaining or that I always have to be right.
The problem here is that I would bet everyone on this forum would *know* I'm right to recommend against doing direct development on the shared SQL sever - but can any of us find any articles or web pages that include facts to support it?
If not, how do we *know* we are right? Maybe this is just a personal preference... (just playing devils advocate).
July 15, 2008 at 7:39 am
Seriously, is there anything out there (on the internet) that I can use as the basis to support my recommendation to NOT install Visual Studio on our shared database server - even in a development or test environment?
July 17, 2008 at 2:18 pm
Guess not...
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply