March 1, 2004 at 8:15 am
Greetings!
I'm not sure if this is the place to ask this but, I work for a company who's web site I'm developing with a SQL back end. the company's IT group insists on making me update my database on a development server and then replicate it to our QA server and then finally replicate it again to our live server.
This has been troublesome and time consuming - especially since I am building web based tools to edit the db. My feeling is that since I control from my tools what is shown on the site wouldn't it make more sense to edit the db on the live server and do away with the replication across two other servers?
Am I off base with this? Is there a reason why my scheme is bad? They generally claim the replication is for "security reasons"...
Thanks for any insight...
Geo
March 4, 2004 at 8:00 am
This was removed by the editor as SPAM
March 4, 2004 at 9:55 am
Depending on the change it might be a bit much, however I wish our site had that much control over what goes on the production server. I don't like to see any change made to a production box that has not been fully tested. What if a mistake is made? Better to catch this in test (I assume you test the change) or to catch in QA (where others may catch it) as opposed to potentiall causing production to crash.
Imagine a want to add a trigger to a table. So I add the following:
CREATE TRIGGER trHistory ON [dbo].[Employees] FOR INSERT
AS
INSERT INTO dbHistory.dboEmployeeHistory (EmployeeID)
SELECT EmployeeID
FROM inserted
When what I meant to add was
CREATE TRIGGER trHistory ON [dbo].[Employees] FOR INSERT
AS
INSERT INTO dbHistory.dbo.EmployeeHistory (EmployeeID)
SELECT EmployeeID
FROM inserted
Both compile properly but when I test the first trigger, if I
had created the table dbo.EmployeeHistory and not the table
dboEmployeeHistory I will get an error. If I did this in
production I have to scramble to fix this.
Better to have a test system to verify that I did this correctly.
Francis
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply