Visual Studio 2010 includes Entity Framework (EF) 4. Knowing what EF 4 is about and having an idea of how to use it can help you decide whether you want to add EF 4 to you SQL Server development toolkit.
At TechEd 2010 I had the opportunity to talk with several of the development tools vendors. So many vendors mentioned that database design should be in the hands of developers rather than DBAs that it’s looking like a trend. An ominous trend based on the supposition that DBAs don’t really understand coding and the development process....More
Visual Studio 2010 includes Entity Framework (EF) 4. Knowing what EF 4 is about and having an idea of how to use it can help you decide whether you want to add EF 4 to you SQL Server development toolkit....More
Throughout this series of posts I’ve taken a somewhat pessimistic view of how SQL Server Agent jobs are managed within most organizations – meaning that most of the code and examples I’ve provided up until this point were based on assumptions about how CHANGE to jobs is managed. That pessimism, to date, has come in two forms:...More
In this series of posts I’ve called out some of the concerns related to SQL Server AlwaysOn Availability Groups and their interaction with SQL Server Agent jobs – both in the form of Batch Jobs (see post #3) and backups....More
When I initially decided to write about AlwaysOn Availability Groups and SQL Server Jobs, I knew I’d have a bunch of different posts on a variety of different topics. To that end, I initially planned on this series of posts being comprised of 3 main parts:...More