SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


To OTAP or not to OTAP?


To OTAP or not to OTAP?

Author
Message
FreeHansje
FreeHansje
SSCrazy
SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)

Group: General Forum Members
Points: 2597 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
Lynn Pettis
Lynn Pettis
SSC Guru
SSC Guru (94K reputation)SSC Guru (94K reputation)SSC Guru (94K reputation)SSC Guru (94K reputation)SSC Guru (94K reputation)SSC Guru (94K reputation)SSC Guru (94K reputation)SSC Guru (94K reputation)

Group: General Forum Members
Points: 94291 Visits: 38955
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)
Ignacio A. Salom Rangel
Ignacio A. Salom Rangel
SSCertifiable
SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)

Group: General Forum Members
Points: 6510 Visits: 1439
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

Ignacio A. Salom Rangel
Ignacio A. Salom Rangel
SSCertifiable
SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)

Group: General Forum Members
Points: 6510 Visits: 1439
FreeHansje (11/19/2012)
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?
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

FreeHansje
FreeHansje
SSCrazy
SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)

Group: General Forum Members
Points: 2597 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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search