jump to navigation

Identifying fragmentation level in SQL Server 2005 and 2008 March 22, 2009

Posted by Arshad Ali in Database Administration, DBA, SQL Server, SQL Server 2008, SQL Server New Version.
add a comment

Identifying fragmentation level in SQL Server 2005 and 2008

While indexes can speed up execution of queries several fold as they can make the querying process faster, there is overhead associated with them. They consume additional disk space and require additional time to update themselves whenever data is updated, deleted or appended in a table. Also when you perform any data modification operations (INSERT, UPDATE, or DELETE statements) index fragmentation may occur and the information in the index can get scattered in the database. Fragmented index data can cause SQL Server to perform unnecessary data reads and switching across different pages, so query performance against a heavily fragmented table can be very poor.
Refer this link to learn more details about fragmentation and different queries to determine the level of fragmentation.



Debugging T-SQL in SQL Server 2008 SSMS March 22, 2009

Posted by Arshad Ali in Database Administration, DBA, SQL Server, SQL Server 2008, SQL Server New Version.
add a comment
Debugging T-SQL in SQL Server 2008 SSMS
If you recall your days working with SQL Server 2000, you would remember debugging a routine (Stored Procedure, UDF and trigger) in Query Analyzer, as a debugger tool was available with it. Starting with SQL Server 2005, Query Analyzer and Enterprise Manager had been clubbed together as SQL Server Management Studio (SSMS). Though this single interface has simplified working with SQL Server, one major drawback was, it does not allow you to debug a routine from there. For that purpose you needed Visual Studio (Enterprise and Professional) edition installed, on your development machine, which allowed you to debug a routine. The requirement to install Visual Studio is something that database developers and DBAs would be reluctant to do as it requires additional funds for a Visual Studio license and puts additional pressure on the physical box after installation. Thankfully Microsoft SQL Server team decided to provide this feature in SQL Server 2008 SSMS.
Refer this link to learn more details about it.

Migration Strategies for SQL Server 2008 March 22, 2009

Posted by Arshad Ali in Database Administration, DBA, SQL Server, SQL Server 2008, SQL Server New Version.
add a comment

Migration Strategies for SQL Server 2008

SQL Server 2008 delivers a powerful set of capabilities to solve the growing needs of managing data in the enterprise, on desktops, and on mobile devices, it also builds on the strong momentum in the business intelligence market by providing a scalable infrastructure that enables information technology to drive business intelligence throughout the organization and deliver intelligence where users want it. SQL Server 2008 also delivers improved performance in many areas, including data warehousing, reporting, and analytics. So if you make the decision to upgrade to 2008, there are a number of tools that make the process easier, but you still need to understand what things you should consider.
Refer this link to learn more details about it.

Microsoft plans for SQL Server 2010 (codename "Kilimanjaro") December 18, 2008

Posted by Arshad Ali in Gemini, Kilimanjaro, Madison, SQL Server 2010, SQL Server New Version.
add a comment
After SQL Server 2008, Microsoft plans for SQL Server 2010 codename “Kilimanjaro” which has been slated for release in first half of 2010. The new version of SQL Server will be focused on business intelligence and will further enrich SQL Server’s BI (business intelligence) capabilities while providing a robust and scalable data platform, capable of supporting the largest BI deployments. Kilimanjaro will provide the foundation for Microsoft’s first data warehouse appliance, code-named Madison, and a BI tool called Gemini that’s being designed to bring a broader range of employees into the BI fold(These are new capabilities and not a rewrite, rework, or upgrade). First CTP version is scheduled to be released within next 12 months.

Gemini will focus on delivering new capabilities in the area of managed self-service analysis capabilities (Self service analysis and Self-service reporting) through “deep integration” with Microsoft’s SharePoint Server and Excel. It will allow information workers to better “slice and dice data and create their own BI (business intelligence) applications and assets to share and collaborate on from within the familiar, everyday Microsoft Office productivity tools they already use.” Another key feature of Gemini is in-memory BI, which analyzes large amounts of data in memory in order to speed performance.

In design of Madison, Microsoft will use data warehouse technology from its recent acquisition of DATAllegro. Madison is designed to deliver massively increased scalability, capable of supporting the very largest data warehousing deployments. The solution will be able to handle the most demanding data warehousing workloads spanning hundreds of terabytes of data and thousands of concurrent users at the low total cost of ownership (TCO). Customers will be able to grow their Madison data warehouses by using a “scale out” approach of adding on standard server boxes as they need them.

Further augmenting the enterprise-class capabilities of Microsoft’s data platform, the acquisition of data quality vendor Zoomix will help provide richer data quality capabilities in future versions of SQL Server Integration Services, enabling customers to maximize the accuracy of their BI.

Microsoft is working with industry-leading server and storage hardware providers including Bull, Dell Inc., EMC Corp., HP and Unisys Corp. to build a strong ecosystem providing an “appliance-like” buying experience for customers based on the “Madison” solution. Soon, customers can expect new data warehouse reference configurations based on SQL Server 2008 from these hardware partners as well.

PS: This time also Microsoft has borrowed the codename “Kilimanjaro” for SQL Server 2010 from the name of a National Park as it was the case with codename “Katmai” for SQL Server 2008. 🙂
For more details refer to: