Editorials

Justifying Best Practices

Great Whitepaper Available
Working with SSIS? If so, check out the white paper we have in the library that talks about how you can use SSIS to do quite a bit more than just an import of your data. Tips, tricks and lot more — learn about why SSIS really does the ETL – Extract, Transport and Load for SQL Server.

> More information here.

Justifying Best Practices
We had an interesting conversation with several speakers and an attendee or two about best practices, and how you justify and explain them to management. A few times this came up – one example was how do you explain that, even though you have security in place, even though you have a beefy server, you shouldn’t have SQL Server on the same box as your web server?

How do you convince people to take the time to test for injection and to protect against it from get-go?

We talked about how you can present the "why" behind all of these, but I suspect that if a manager isn’t getting the basic premise of industry-standard best practices that are well-documented (probably for a reason), that they wouldn’t necessarily understand a more detailed discussion. It goes well beyond the whole "if they don’t get it, they will soon when things break!" I say this because it’s a nice sentiment at times, but it’s not realistic if you plan to retain your job.

How do you present items like this to management and help them really understand the things they need to know, especially given they don’t *want* to know the details?

One approach I’ve seen is to show case studies – summarize it as a reference item and include it with an overall package of information. I’m a big fan of a one-page cover letter making your points, then pointing to the backup materials, also included in the package. That way, they can read what you’re trying to explain if they want to, they can see that you’ve taken the time to research it, and it’s not just your opinion.

Do you have other techniques? Drop me a note – let me know

Managing Change with Your SQL Server
We’ll look into what options you have for managing change – from documenting your systems to how triggers work and how you can apply to them to your databases as an audit measure. We’ll also investigate other technologies you’ll want to know about when considering how you control and manage change with SQL Server.

> Register Now
> Live date: 3/11/2008

Featured White Paper(s)
Windows PowerShell: Why Developers Should Care
Windows PowerShell is Microsoft’s next generation scripting and shell tool. Find out more about this tool and why its importa… (read more)

Structuring the Unstructured: How to Dimensionalize Semi-Structured Business Data
The Business Intelligence industry is paying more and more attention to the ever-growing heap of unstructured and semi-struct… (read more)