Featured Article(s)
Introducing the ADO.NET Entity Framework
This article takes a look at the ADO.NET Entity Framework, its features and benefits. It also discusses why it promises to be the technology of choice for the next generation of data access using ADO.NET. The primary objective of the ADO.NET Entity Framework is to objectify your applications data – add a level of abstraction on top of the relational model. In raising this level of abstraction, you can isolate the logical model of your application’s data from the relational model.
Frustrated Looking for Real Answers?
We’ve seen time and time again how getting the right information, at the right times, can be a huge multiplier for your efforts. From knowing where to look for debugging help to new techniques to best practices, sometimes just knowing you can see a quick demonstration means you don’t have to beat our head against the wall. This is why ITUplink.com exists. Now more than 40+ hours (10 hours added just this week) of specific, targeted, focused how-to information that you can apply immediately – all online, all the time. Check it out here.
Your Opinions of SQL Server 2005/8 Changes in Maint. Plans
Now that you’ve had time to work with the newer releases of SQL Server, I’d be curious what you think of the new approaches to maintenance plans for SQL Server. Previously, it was a series of jobs and steps that were created, now it’s more of an automated job in SSIS.
This has of course brought about several changes. First, when you need to make changes, the interface is substantially different. You’ll be working with flow-type access to the plan, what it does and how it responds to "normal" flow and exceptions.
Second, it means the wizard-type tools are solid for getting the plan going, but modifications to the plan will be more in a "native" environment. This leaves several items to be learned, sometimes the hard way. Chris Shaw has a webcast coming up (stay tuned for the announcement) where he goes through some of the things that can come up in this type of environment. What happens when things don’t go as planned, what if you want to add a branch to the flow, or update a specific component step…?
So what do you think – do you like the latest approach to the maintenance plans (specifically) better than the prior approach? Some have said that the wizard hid too much from the DBA, that it was painful to make updates in some cases and indeed the flow of the plan wasn’t as controllable, at least using the wizard, as it needed to be. Do you agree?
Drop me a quick email, let me know how you’re approaching this and what your opinions are on the different tools.
Featured White Paper(s)
Enhance SQL Reporting Services with Double-Take
Microsoft SQL Reporting Services is an exciting way for organizations to gain access and insight into their important busines… (read more)