give 'em an hourly data dump and a script to do the import and don't let them touch the real systems. Show them the gui tools for MySQL and then laugh. Any DBA worth their paycheck can be function in MySQL in a week using a book like SQL in a Nutshell combined with the main docs for MySQL (which are very good!).<br>
<br>If they screw up, convert the mess to Postgres with SELinux extensions and give 'em an ODBC connection from MSAccess.<br><br><div class="gmail_quote">On Mon, Aug 23, 2010 at 10:53 PM, Mike Harrison <span dir="ltr"><<a href="mailto:cluon@geeklabs.com">cluon@geeklabs.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">> They have DBAs that only know MS SQL. If he can replicate between the<br>
> two then the DBAs can backup the slave (MS SQL) and use their Crystal<br>
> Reports against the data. The will _NOT_ be able to do update, insert,<br>
> delete, or alter on any rows in the MS SQL database.<br>
<br>
</div>And that's perfectly fine...and the way it should be. :)<br>
<div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>-- <br>James P. Kinney III<br>I would rather stumble along in freedom than walk effortlessly in chains.<br><br><br>