The Weekly SQL Server Show – Watch Now
The current show is an interview with Kim Tripp and Paul Randal. We got together at DevConnections in Las Vegas and talked about everything from the famous board game to SQL Server 2008.
Browser-Based Compare, Synchronize and Audit Tool
This is pretty cool – this tool will compare and script out changes to synchronize databases and objects, build transaction-enabled, optimized synchronization scripts that include rollback and more. You can even audit databases to keep track of changes, all from your web browser. No application software to install on the workstation. Take a look here – there is a trial version too so you can use it on your own systems to see how it works. Nice options!
Managing Change with SQL Server
We’ll look into a few different things to know about working with change and your SQL Server. First, we’ll look at how to document your schemas and database options. Next, we’ll look at how you can log changes, by looking into Triggers and some basic security options to have to block unauthorized change in your databases. There are a number of options you have, and we’ll provide the information you need to know when it comes to managing change to your systems.
> Register Now
> Dec 5 2007 12:00pm Noon Pacific
Do "Compliance" Systems Apply to Smaller Systems?
I’ve talked on the show several times about people pulling information from compliance requirements and using that as a starting point for determining best practices for their own installation, even if the installation didn’t fall under the "rules" of compliance. The reason I’ve approached it this way is because, even if you don’t agree with all aspects of the compliance regulatory guidance (yeah, that’s it, GUIDANCE) on database implementations, you can surely find some things to think about in there.
So, my question to you this first day back from the US holiday of Thanksgiving is, do you find yourself getting good guidance from the compliance requirements – even if they may not directly apply to you specifically – in terms of best practices? I’ve seen good information on separating DBA and developer roles, good information on backup and recovery requirements and the like. While the compliance implementations are "expensive" in terms of resources required to implement them, the points that are made, and the functional changes that can be applied to your systems can be really helpful.
What do you think? Do you, have you, or would you use compliance-type regulations as places to start, or at the very least food for thought, on what you should be paying attention to with your systems?
Drop me a note, let me know how you approach it.
Featured White Paper(s)
Microsoft SQL Server Cluster Vs Standby Server
This paper discusses specifically two out of various options available for SQL Server high availability, Microsoft SQL Server… (read more)
A simple solution to scripting when sysdepend is damaged
Damaged dependency information is a common problem when a database has a reasonable number of objects. This article explains … (read more)
Database Change Management and Version Control
An automated methodology is a complete end-to-end solution for database change management and version control, which minimise… (read more)
IT Director’s Reference Series: Practical Guide to Sarbanes-Oxley IT Internal Controls
Sarbanes-Oxley is the most comprehensive financial regulatory law in US history. It places responsibility for accurate and re… (read more)