Boris Baliner


SQLServerCentral Article

SQL 2000 to SQL 2005: Where have all the old features gone?

SQL Server 2005 is out and everyone is moving to test and deploy it. However many people are still managing SQL Server 2000 instances. New author Boris Baliner brings us a few tricks to find that information you are used to from Enterprise Manager.

4 (1)

You rated this post out of 5. Change rating

2007-10-02 (first published: )

35,479 reads

SQLServerCentral Article

Quickly Viewing Available Space

As everyone moves to SQL Server 2005 from SQL Server 2000, there are quite a few pieces of information that have moved and may give you trouble finding. Boris Balinger brings us a followup to his first look at some of those changes with a quick article on how you can get the free space in your database files.

4.67 (3)

You rated this post out of 5. Change rating

2006-06-06

9,343 reads

Blogs

Time to Revive our YouTube Channel

By

It’s been forgotten about and neglected for few years but I’ve decided to dust...

Microsoft MVP 2025: Continuing the Data Platform Journey

By

I am honored to announce that I have been renewed as a Microsoft MVP...

What is KTLO? Keep The Lights On vs Project Work in Agile

By

🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

Navigating Multi Platform Realities in My Database Life

By dbakevlar

Comments posted to this topic are about the item Navigating Multi Platform Realities in...

Import/Export SSMS Settings issue

By Brandie Tarvin

I have tried a number of times to export and then import my SSMS...

Visit the forum

Question of the Day

Query Plan Regressions --

For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question:  You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?

See possible answers