Featured Article(s)
Handling Concurrency issues in ADO.NET (Part II)
This is the second and the concluding part in this series where we will discuss the types of concurrency and the best practices in choosing and working with them.
Latest SSWUGtv:
Mock Interview, Part II. The Technical Interview: Go through the interview process, questions, answers and interpreting the responses. Learn About Questions, Answers and Tips for a Great Experience.
> Watch the show here
Also, don’t miss:
Watch: Microsoft’s Matt Nunn on SQL Server, Visual Studio, features, roles and disciplines.
Watch: Handling a DBA interview. A Mock interview with questions, answers and more.
Automate Rollouts & Deployment of Changes
I’m a DBA. My developers and QA engineers pass me code and scripts that need to be deployed in production. Connecting to all the databases and servers and pushing the updates takes forever. And the same thing happens with every project and release. Does this sound familiar? Well… the good news is that now there are tools that completely automate this process – passing projects and code from dev to QA and production with one-click deployment on all databases in each environment. Check out SQL Farms – it’ll help you get the job done, across servers, with a single click.
Are You Open to Version 1.00?
People have long said that they’d be less-inclined to install version 1.00 of products, ranging from SQL Server to Windows to, well, just about anything.
I’m curious if you think this has changed? Specifically, what are your plans for SQL Server 2008, Windows 2008, VS 2008? Many have said they particularly consider SQL Server 2008 a update to SQL Server 2005 (I disagree, but that’s a subject for another day) and it got me wonder if this new approach of more frequent releases and incremental builds in functionality has you more comfortable installing the releases as they come out?
Without sounding like a complete mouthpiece, I do have to say that it seems like the dev cycles and testing processes, along with the overall development and feature approach has really worked well of late for Microsoft. I’m really impressed with how they’re doing things – adding features to the source path as the features are mature and ready to go rather than waiting on a product feature suite that "must" happen. It has me, personally feeling pretty comfortable with things. Add to this the test of SQL Server 2005, you can see it’s been a really stable release.
Sure, there are issues in all releases. But really – it’s done really well.
So, there’s my topic of debate. Are you a version 1.00 person for SQL, Windows and VS 2008?
Drop me a note here, let me know.
Understanding Indexes and Index Fragmentation
In this webcast, we’ll examine how to look at your indexes, how to understand them and how to apply them. We’ll look into fragmentation and how you can determine whether an index needs to be rebuilt. We’ll look at the options you have available to you for maintaining your indexes as well.
> Register Now
> Dec 11 2007 12:00pm Noon Pacific
Featured White Paper(s)
Troubleshooting SQL 2005 – Opening a Database Administrator’s Toolbox
This white paper guides you through troubleshooting using some of SQL 2005’s built-in features to diagnose issues with your d… (read more)
The Why, What and How of Migrating Lotus Notes Applications
Organizations looking for solutions to migrate their Lotus Notes applications and developers from groupware like Lotus Notes … (read more)
Accelerating Access to Enterprise Files over the WAN
In enterprises today, there is a growing need to share and co-develop documents and files of various types. These include gen… (read more)
Enterprise Strategies to Improve Application Testing
Reliable applications come from reliable testing – and realistic test data plays a key role. Many organizations clone or copy… (read more)