Its really amazing to find something for free, isnt it? and if its going to make work life easy and more productive then make more sense! Here goes a post from Eric about Large collection of Free Microsoft eBooks for you, including: SharePoint, Visual Studio, Windows Phone, Windows 8, Office 365, Office 2010, SQL Server 2012, Azure, and more.
go to: Link
Microsoft on july 26th announced that SQL server 2008 R2 service pack is now available to download. If you apply this service will upgrade SQL build version to 10.50.4000.0; Also visit this link to find what all bugs have been fixed in this service pack.
Posted by Deepak Kumar | Posted in SQL BI/DW/SSRS, SQL DBA, SQL Dev | Posted on 21-03-2011
On any given production environment a SQL DBA must follow set of best practices to ensure smooth and highly optimized databases availability. Here are few common mistakes that I have identified and would recommend to fix if you have encountered or seeing anything similar.
1. Not preparing and validating a reliable backup and recovery policy with backup files retention period for databases as per agreed data loss and application downtime it may cause while recovering databases.
Got bored reading Books, PDF files, Articles, Web pages, RSS? Need a change in learning resources? Get more learning from SQL Videos & Demos! 100s of High tech videos explaining how to do, deep dives and internals. Must to watch, download for your free time!
SQL Server 2008 Videos and Demos Link
SQL Server 2005 Videos and Demos Link
SQL Server 2008 Microsoft Certified Master (MCM) Readiness Videos Link
SQL Server 2008 Demo Videos and Webcasts Link
SQL Server 2005 Express for Beginners Link
SQL Server 2005 Database Administration Link
Please post or comment, If you have more links to be included.
I have no words to explain my excitement and happiness to share news with you all – my book on SQL Server 2008 High Availability is published!!
I have started authoring this book in May 2010 and as the time passes and gradually I move to the final chapter of the book, I was feeling like aha finally it is done!!! – Do you think so, it was this easy? No, every publication house has their own set of rules to be followed while authoring a book and a process to be followed before the chapter or entire book is ready to be published i.e. 1st edit, 2nd edit of the chapter until final edit and the Packt Publication is no exception.
Do you have something to write about SQL Server that can help SQL community by your learning, innovation. R&d, research etc. This is an unique opportunity to reach a large group of SQL Server users, gain experience as SQL writer, publicity and much more.
Drop an email with your content/summary to email@example.com I will review and publish your content on SQLKnowledge.com by your name and provide you instant website access to review, modify & answer user comments on website.
Your comments & suggestions are welcome; Feel free to reply if you have any questions
As a Proactive DBA, you must monitor All SQL Server errors having severity level between 17 to 25. Any errors from level 20 to 25 are serious in nature however for 17 to 19 a DBA involvement is required for resolution. Here is self explanatory MS description of error levels, steps to get automatic alert as soon as any of error occurs and list of error messages.
SQL profiler is an excellent tool for T-SQL query performance optimization. SQL Server Production DBA’s use Profiler to scan what T-SQL queries are getting executed inside SQL Server and what are the queries that can be filtered for further fine-tuning. SQL profiler has inbuilt scheduler for stopping a trace, but Trace Properties does not provide functionality to automatically schedule a trace and keep it running for a desired frequency.
There are some condition & times when SQL Server CPU utilization exceeds threshold value (ex 80% or more) and stay constant even till 100% for a undefined duration. A DBA do not get notified automatically about performance degrade until its reported by application team or service desk . This usually happens when all in sudden unpredicted application workload goes to SQL Server for processing; but at good number of times, its because of some T-SQL Queries are taking longer than expected or because of bad execution plan or blocking. There may be more reason to add, but ultimately high CPU utilization on production systems is going to hurt performance.
As a proactive DBA its one of responsibility to keep an eye on database’s growth and other file system changes for the databases hosted on SQL instance. However being busy on daily DBA tasks, its not always possible to prepare scripts or manually extract data from system for documentations & trend reporting purposes. I faced the similar challenge while working with large DB systems and came up with a T-SQL script that can do the needful without worries..