Not sure I am in the right place here but thought I would ask an open
question. We have an IIS website, mainly ASP files, .NET 1 & 2, this
is located in our DMZ. It connects back into the LAN using using port
1433 to our SQL 2000 server.
As the Sysadmin I try to ensure our development team only work on the
development SQL & IIS boxes but this is becoming more difficult by the
day. Very soon I am moving the production servers to a data center so
obviously any problems would cause extensive downtiume due to
distances I have to travel..
How do you all deal with the developer idea that you must work on live
servers during working hours? My view is that any bugfixes or software
release's should be carried out out of business hours, but I seem to
be hiting a brick wall as I am on my own..
CheersYou can setup a test site that will run a copy of the production code
connected to a copy of the production database. Once changes are tested
there, they can be deployed to production in after hours.
--
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]
http://msmvps.com/blogs/egoldin
http://usableasp.net
"gstar" <gary.brett@.gmail.comwrote in message
news:1192613674.844412.184910@.e9g2000prf.googlegro ups.com...
Quote:
Originally Posted by
Hi,
Not sure I am in the right place here but thought I would ask an open
question. We have an IIS website, mainly ASP files, .NET 1 & 2, this
is located in our DMZ. It connects back into the LAN using using port
1433 to our SQL 2000 server.
>
As the Sysadmin I try to ensure our development team only work on the
development SQL & IIS boxes but this is becoming more difficult by the
day. Very soon I am moving the production servers to a data center so
obviously any problems would cause extensive downtiume due to
distances I have to travel..
>
How do you all deal with the developer idea that you must work on live
servers during working hours? My view is that any bugfixes or software
release's should be carried out out of business hours, but I seem to
be hiting a brick wall as I am on my own..
>
Cheers
>
"gstar" <gary.brett@.gmail.comwrote in message
news:1192613674.844412.184910@.e9g2000prf.googlegro ups.com...
Quote:
Originally Posted by
How do you all deal with the developer idea that you must work on live
servers during working hours? My view is that any bugfixes or software
release's should be carried out out of business hours, but I seem to
be hiting a brick wall as I am on my own..
I have three environments: dev, test and live.
Developers don't need to work on live servers - they may, however, need to
work on real data, in which case synchronise the live database(s) with the
dev and/or test database(s) at the beginning of the working day.
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
Quote:
Originally Posted by
I have three environments: dev, test and live.
>
Developers don't need to work on live servers - they may, however, need to
work on real data, in which case synchronise the live database(s) with the
dev and/or test database(s) at the beginning of the working day.
>
--
Mark Rae
ASP.NET MVPhttp://www.markrae.net
Thankyou for you replies.
I too have dev, staging & live enviroment, thats what makes it so
annoying! They say if the MD needs a report in the middle of the day
or a customer rings in with a bug, it needs fixing on live right then!
I like the idea of synchronising the live data to the staging server,
is it easy to achieve, is that possible over the WAN? As you can see
we dont have a DBA so I am trying to firefight here! I also dont want
to sync the structure, just the data?
Again thankyou for your time, I know you must have answered questions
like this before..
"gstar" <gary.brett@.gmail.comwrote in message
news:1192617287.830568.9160@.y27g2000pre.googlegrou ps.com...
Quote:
Originally Posted by
They say if the MD needs a report in the middle of the day
That's not a bug, though! Why can't the MD use the live system...?
Quote:
Originally Posted by
or a customer rings in with a bug, it needs fixing on live right then!
No! Staging and live must be running the same code, right? Otherwise there's
no point.
You really need to stand your ground here, and say the following:
If a customer rings in with a bug, it needs fixing on dev, testing on
staging and then deploying to live. If you can't deploy to your live system
during business hours, then you most certainly can't bug fix on your live
system either...
If your management is unable to see the rationale for this, then I strongly
suggest you look for another job. Hacking about with live systems is a sure
recipe for disaster - and when the disaster inevitably happens, who do you
think will get the blame...?
Quote:
Originally Posted by
I like the idea of synchronising the live data to the staging server,
is it easy to achieve, is that possible over the WAN?
Sure - why not? You just need a tool which can connect to both your live
database(s) and your staging database(s). I use this:
http://www.teratrax.com/. This is also very popular:
http://www.red-gate.com/index.htm?g...CFRoGEgodyUi6eg, but it's
a bit more expensive. You can even write your own tool in raw T-SQL if
you're really strapped for cash, but why reinvent the wheel...?
Quote:
Originally Posted by
As you can see we dont have a DBA so I am trying to firefight here!
In the words of Tom Jones, it's not unusual... :-)
Quote:
Originally Posted by
I also dont want to sync the structure, just the data?
Both the products I mention above will do that.
Quote:
Originally Posted by
Again thankyou for your time, I know you must have answered questions
like this before..
All part of the service... :-)
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
As Mark indicated, I wish I had a dollar for every time a disaster happened
because some developer was "fixing" something on a production web site and
they blew it because their fix didn't go through a sane testing process.
-- Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com
"gstar" wrote:
Quote:
Originally Posted by
Hi,
Not sure I am in the right place here but thought I would ask an open
question. We have an IIS website, mainly ASP files, .NET 1 & 2, this
is located in our DMZ. It connects back into the LAN using using port
1433 to our SQL 2000 server.
>
As the Sysadmin I try to ensure our development team only work on the
development SQL & IIS boxes but this is becoming more difficult by the
day. Very soon I am moving the production servers to a data center so
obviously any problems would cause extensive downtiume due to
distances I have to travel..
>
How do you all deal with the developer idea that you must work on live
servers during working hours? My view is that any bugfixes or software
release's should be carried out out of business hours, but I seem to
be hiting a brick wall as I am on my own..
>
Cheers
>
>
All comments taken on board and appreciated, it has helped me to
decide our approach and given me some much needed confidence that I am
doing the right thing!!
I really like the Teratrax product, have tested and it does the job
brilliantly. I cant see a method to automate this to occur each day at
a certain time and sync the servers without any input, will look
further into it later, but do you know if thats possible?
Ta
"gstar" <gary.brett@.gmail.comwrote in message
news:1192632161.267613.108730@.q5g2000prf.googlegro ups.com...
Quote:
Originally Posted by
I really like the Teratrax product, have tested and it does the job
brilliantly. I cant see a method to automate this to occur each day at
a certain time and sync the servers without any input, will look
further into it later, but do you know if thats possible?
Ah, no - I don't think so...
This type of tool really is really aimed at ad-hoc development tasks rather
than regular and scheduled production tasks.
Luckily, though, if you need regular replication between production and
staging, then SQL Server already has this built-in:
http://www.google.co.uk/search?sour...%22+replication
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
Ah, no - I don't think so...
Quote:
Originally Posted by
>
This type of tool really is really aimed at ad-hoc development tasks rather
than regular and scheduled production tasks.
>
Luckily, though, if you need regular replication between production and
staging, then SQL Server already has this built-in:http://www.google.co.uk/search?sour...n-GB&ie=UTF-8&r...
>
--
Mark Rae
ASP.NET MVPhttp://www.markrae.net
OK, I guess I could run it manually each week to uopdate the data
locally. I have however run into a few problems so I may also try Red-
Gate, on the first DB I attempted to synch it reported that out of 47
tables 23 had no primary key so could do anything with it!. I have
asked the dev team why, but they shrugged their shoulders.. Helpful
eh?
Cheers
Gary
"gstar" <gary.brett@.gmail.comwrote in message
news:1192695378.155635.135600@.i13g2000prf.googlegr oups.com...
Quote:
Originally Posted by
OK, I guess I could run it manually each week to uopdate the data
locally.
As mentioned, these are very much tools for ad-hoc work. Once I've set up
the various tasks (TeraTrax calls them "projects"), I only ever run them on
a need basis... For regular synchronisation, I use replication - that's what
it's for...
Quote:
Originally Posted by
I have however run into a few problems so I may also try Red-
Gate, on the first DB I attempted to synch it reported that out of 47
tables 23 had no primary key so could do anything with it!. I have
asked the dev team why, but they shrugged their shoulders.. Helpful
eh?
You're wasting your time with this company...
I suggest you show your boss this thread...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
0 comments:
Post a Comment