Webcast: Protect & Defend Your Data
With most SharePoint implementations storing critical business data, it is crucial that this data be protected and quickly restorable in the event of a disaster. Learn how utilizing Data Protection Manager 2007 as your backup/restore/disaster recovery solution provides a full-fidelity solution with granular control. We will walk you through the initial configuration of DPM as well as setting up a recovery farm. Presented by: Christopher Regan
Webcast: 7 SQL Server development practices more evil than cursors
Cursors do indeed cause performance issues, but cursors are easy to correct. This session addresses the problem of cursors and then uncovers 7 common practices that are more costly than cursors Based on several years of consulting specializing in optimizing third-party ISV databases, the list of worst practices range from critical database design blunders to indexing errors to T -SQL faux pas’. Avoiding the blunders on this list will be the difference between a successful database project and a failure. Not to leave you in the dark, this session will contrast every evil practice with a best practice to solve the problem. Presented by: Paul Nielsen
DBASchool – Register Now
3-day course about what really matters for working with SQL Server. Security, performance, disaster recovery, TSQL and a lot more.
[Get more information here]
Need Justification for Time/Funds for Security?
All you need to do is take a look at this report from VerizonBusiness.com. There are a number of things that stand out in this report. The first of these is that they break out breaches by internal and external sources. An awful lot of people will ignore the internal threats since they can be both more difficult to prevent (people internal to your company generally have more liberal access just because they work there) and because you want to trust your company employees.
Having the internal threat isn’t necessarily what you may think… If you look at the top issue they list for data breaches, it’s actually pertaining to user credentials, ease of guessing passwords and the like. You can solve this one with Windows by forcing a password complexity model on the user accounts for your systems and following up with expiring passwords so they must be updated on a regular basis.
The second item on the list though is injection. Out of all of the different breaches out there, *SQL injection* is the second biggest culprit for data loss. Yikes! If you’re working with SQL Server (and if you’re not, this may be the wrong newsletter and site for you), and not protecting against Injection with the array of options you have available to you, it’s clearly time to get busy. Find out about filtering, error messages, what you can do with stored procedures, etc. It’s a matter of deciding to prevent it rather than guessing. It’s like deciding not to have a lock on your front door because people won’t notice you don’t have locks on your doors… so they won’t break in. Wrong.
If we could change one thing in the database profession over the next year, it would be great if we could address injection on systems before it happens, rather than as a response to an attack succeeding. So much of injection prevention work is done as a response to someone hacking in – rather than reactive, we’ve got to help people get proactive. Check out that report – imagine if the injection line item on page 17 went away. Nice.
Featured White Paper(s)
15 Minute Guide to Building Efficient Infrastructures for Microsoft SharePoint Server
Read the guide to learn how to build efficient infrastructures for Microsoft SharePoint Server environments-whether physical… (read more)