I was informed by the owner of the site that my videos have just went live. I've spent quite a number of days working on the videos to make sure that subscribers will get as much as they can in their pursuit of learning about SQL Server 2008. I would appreciate your feedback on what else you would like to see on the video list
Check out the BlogCastRepository website for my SQL Server 2008 videos. I'll come up with SQL Server 2005 videos as well in the future
Wednesday, June 18, 2008
Saturday, June 7, 2008
Exploring Database Backup Compression in SQL Server 2008
Database backup size is always an issue in very large databases. Which is why we plan our backup and restore procedures properly to include either differential and filegroup backups. Most of the times, we use backup compression tools like LiteSpeed for SQL Server from Quest or SQL Backup from RedGate. SQL Server 2008 has a built-in compression engine for you to compress your database backups. I have written an article about this feature in MSSQLTips.com and created a video at BlogCastRepository.com
Monday, June 2, 2008
So, you think your secured, patched and updated servers are secure?
So, we patch our servers, subject them to numerous security scans, implement security best practices and expect them to be secured? That's ridiculous.
I have been trying to convince developers how a functional application can be vulnerable if they do not implement security best practices in writing codes. I come from a developer background as well and with tight and unreasonable deadlines, developers are only concerned with functionality and nothing more. But with the increasing incidents of websites being defaced because of SQL injection attacks, there's no doubt that as long as applications are running on servers, there will always be security vulnerabilities. SQL injections attacks are no respecter of platforms nor database engines. So better have a look at your application codes.
A Microsoft blog post on SQL injection attack is available here.
I have been trying to convince developers how a functional application can be vulnerable if they do not implement security best practices in writing codes. I come from a developer background as well and with tight and unreasonable deadlines, developers are only concerned with functionality and nothing more. But with the increasing incidents of websites being defaced because of SQL injection attacks, there's no doubt that as long as applications are running on servers, there will always be security vulnerabilities. SQL injections attacks are no respecter of platforms nor database engines. So better have a look at your application codes.
A Microsoft blog post on SQL injection attack is available here.
Friday, May 30, 2008
Encrypting your database backups in SQL Server 2008
I was asked a question about how you make sure that your SQL Server database backups are secured and I ended up saying, "go get a third-party tool like LiteSpeed for SQL Server from Quest Software." While it is true that third-party tools can provide additional layer of security on your database backups, budget is always a constraint. Good thing SQL Server 2008 has included a feature called transparent data encryption which you can use to secure your database backups. I have a written an article on MSSQLTips.com and created a video at BlogCastRepository.com about this feature which is worth having a look at.
Subscribe to:
Posts (Atom)