Microsoft SQL Server
The purpose of technology is to make life easier and more quality-oriented. It is this virtue of technology that makes it evergreen and sustainable. Its unique feature is its innovative nature. Technology blogging is a way for the technologists to rant about technology and throw light at known and unknown corners with new angles. This Log Buffer Edition covers those angles and more. Enjoy!
The weather is changing, clocks are being adjusted, and the changes at the technological front are as usual rapid, frequent, and over-whelming. Keeping up with such rapid-fire changes is a project in itself. In the database triangle of Oracle, SQL Server, and MySQL, patches, updates, features, tricks, and tips are booming, and so is this Log Buffer Edition.
There is so much to learn out there. So much to accomplish and so much to devour technically. It can be daunting and overwhelming to have so much in one’s plate, and that is why this Log Buffer Edition has culled some top notch blog posts for you in Log buffer #264.
TEMPDB, is one of SQL server hot-debated topics; there’s always something to say about its sizing, file placement or datafiles count in Multi-core instances. This is simply because TEMPDB is a global resource that’s heavily used and very critical asset in a busy instance; this makes any advice against TEMPDB fall in the “It depends” category.
In this Log Buffer Edition, March madness with method continues with plethora of blog posts from across different database technologies. Enjoy this Log Buffer #263.
This week is packed with conference news, birthdays, tutorials, awards, and much more. From Pythian proud recipient of HIO Employer Excellence Award to the health checks of SQL Server, and from hints in stored outlines to the birthday of Paul Vallee, this Log Buffer Edition has it all in Log Buffer #262.
As we all are aware SQL Server 2012 virtual launch has arrived. Earlier I discussed what’s new in SQL Server 2012 setup, MS has released the SQL Server 2012 training kit and made it available for us to download.
I’ve been playing with SQL Server 2012, codenamed “Denali,” since the CTP days and am very happy with some of the features that they have introduced to address high availability and disaster recovery requirements. For me, these are more than enough reasons to consider upgrading to SQL Server 2012.
In recent past we had a situation where in, we were required to move MSDB, Model and Master databases to a new location, the reason being a faulty drive. While moving the system databases to the new location we needed to be extra cautious. Let’s see the process step-by-step.
The process of upgrading SQL Server is usually time consuming, costs money and requires availability of human resources. If you don’t see the immediate need…Why bother?! Before deciding on upgrading, you should be aware of the new features and make sure you will really benefit by the upgrade. From our experience at Pythian with dozens of clients and hundreds of environments, what could be worth upgrading to SQL Server 2012?
Here are some of the top features related to the database engine (Part I):