Featured Article(s)
Using LiveId for SharePoint authentication
Authentication and credentials management is not a trivial thing. You have to ask yourself the following: * How do I handle new user registrations? * What about resetting passwords? * How do I handle "forgot password"? * How do I ensure password complexity requirements? * How should I handle password expiration? * Should an authentication be going through an encrypted connection (SSL)? * Should user login be an email address, or just a name?
New SQL Server Show Posted
SelectViews: RAID and SANs, RAID and Performance, SharePoint Feedback, Industry News and More. Also, Splitting Databases, Transaction Logs for Performance, Maintenance Plans Best Practices and Many Other Tips for Your SQL Server.
[Watch the Show Here]
Webcast: Learn about managing your SQL Server data recovery vulnerabilities
In this session we’ll look into the different options you have available to protect your SQL Server investment. Learn about backup and restore, log shipping, replication and other tools you can use to help reduce risk. Find out what is involved, the pros and cons and where you can go to learn more about each option.
> Register Now to reserve your spot
> Live date: 2/25/2009
Are Your Service Pack Habits Changing?
Microsoft just released some updates and one does apply to SQL Server. It deals with injection, vulnerable systems and users systems, permissions, etc. This has me wondering – have your habits changed or become refined when it comes to applying updates?
Has anything changed wit hyour approach?
For so long it’s been a tough situation to apply service packs. From getting vendors to update their code and certify for a given patch level to your own testing and deployment processes. Clearly, it can be quite the process.
Have you changed your approach? Do you see things stabilizing? I ask because it does seem like, on the whole. the application of updates has gotten much better, at least in our own testing here. The hesitation to blindly install is certainly still there, but the fact is, we’ve seen minor issues, if any, on installation. We’ve been tending more toward applying updates after testing, then of course testing again after installation to make sure all is well.
Is your approach changing? Drop me an email, let me know.
Featured White Paper(s)
Understanding and Interpreting SQL Server Performance Counters
The SQL Server database management system provides many performance counters. However, numerous explanations provided via the… (read more)
Migrating DTS Packages to Integration Services
SQL Server Integration Services (SSIS) brings a revolutionary concept of enterprise-class ETL to the masses. The engine is ro… (read more)