To OTAP or not to OTAP?

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 - General » To OTAP or not to OTAP?

To OTAP or not to OTAP?

Rate Topic

Display Mode

Topic Options

Author

Message

FreeHansje

Posted Monday, November 19, 2012 4:08 AM

SSC Eights!

Group: General Forum Members
Last Login: Thursday, December 06, 2012 8:30 AM
Points: 879, Visits: 810

Currently I am working in an organization, where development and production databases reside in the same SQL Server instance. The main reason for this is ease of management: updates for SQL Server need be applied to less instances and it is easier to move developed objects from D to P...
License costs is mentioned in passing, but they acknowledge this is not a big issue.
Security and autorization is also not an issue, because the people responsible are very careful and know what tehy are doing...

I am looking for arguments in favour of an OTAP, and I realize it si not neccesserry to go to extremes if you ahve a small orgainazarion. My main argument is, I am a fanatical believer in Murphy. Sooner or later the risks of having different environments merged will come to frutations. To me lessening risks is paramount.

What are the thoughts of collegues? Always OTAP? Or it depends on circumstances? Or not really neccesserry?

Greetz,
Hans Brouwer

Post #1386283

Lynn Pettis

Posted Tuesday, November 20, 2012 8:41 PM

SSC-Insane

Group: General Forum Members
Last Login: Today @ 11:07 PM
Points: 21,625, Visits: 27,468

I'm not sure what you are asking here. OTAP makes no sense to me.

Cool

Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)

Post #1387215

Ignacio A. Salom Rangel

Posted Wednesday, November 21, 2012 2:15 PM

Hall of Fame

Group: General Forum Members
Last Login: Yesterday @ 9:36 AM
Points: 3,051, Visits: 1,357

Lynn Pettis (11/20/2012)

I'm not sure what you are asking here. OTAP makes no sense to me.

Lynn, I think he is refering to a DTAP (Development, Test, Acceptance and Production) in Dutch OTAP (Ontwikkeling, Test, Acceptatie and Productie).

My blog

Post #1387609

Ignacio A. Salom Rangel

Posted Wednesday, November 21, 2012 2:26 PM

Hall of Fame

Group: General Forum Members
Last Login: Yesterday @ 9:36 AM
Points: 3,051, Visits: 1,357

FreeHansje (11/19/2012)

My personal opinion is not to place a development database with a production database on the same server. In your case the databases are on the same SQL Server instance what I consider "Extremely" dangerous. You mentiones that "Security and authorization are not an issue, because the people responsible are very careful and know what they are doing...", that will not be good enough to me. What will happend when one of those people working on the databases will make a mistake? Or can you guarantee that they will never make a mistake?

My blog

Post #1387614

FreeHansje

Posted Thursday, November 29, 2012 3:31 AM

SSC Eights!

Group: General Forum Members
Last Login: Thursday, December 06, 2012 8:30 AM
Points: 879, Visits: 810

Tnx for answering, and apologies for the confusion: it is as Ignacio explains, I used the Dutch equivalent of DTAP.

Greetz,
Hans Brouwer

Post #1390383

« Prev Topic | Next Topic »

Permissions