Posts Tagged ‘SSMS’

Sub-Folder Grouping for Folders

March 5, 2009 Leave a comment

When managing large SQL Server instances; the number of databases on a server sometimes start creating a headache to manage. If we can group the SQL Server databases by logical, function, or whatever sub-folder structure we have it can make DBA life easier.

For example we have System Database and Database Snapshot folder. I might want to make a folder for SharePoint Databases and throw all the SharePoint DB in there; for the users it is no different in functionality but for viewing it makes it easier to access (I hope).

Anyhow, ran into this on NewGroup, link.

So I decided to search Microsoft Connect, few people would like something similar. Please go there and vote, link.

Categories: SQL 2005, SQL 2008 Tags:

"No description found" Error when modifying Maintenance Plans

February 19, 2009 Leave a comment

When you are trying to modify a maintenance plan; sometimes you might get “No Description Found” error and you cannot do any work in SSIS when that happens.

Everything was working properly for me until I had to install Microsoft Visio 2003 and I couldn’t update my maintenance plans any more.

In the reference link it explains because of MSXML DLL issue in Visio 2003 RTM edition it causes the issue with SSIS packages. Installing the newest Service Pack for Visio resolves the issue after reboot.

So this is not an issue with SQL Server Egine or SSIS Engine but just the Sql Server Management Studio (SSMS).

I also read an post on SQL Server Central where someone stated they got it to work just after running following commands also:

Regsvr32 “C:\WINDOWS\system32\msxml.dll”
Regsvr32 “C:\WINDOWS\system32\msxml3.dll”

You still have to reboot computer; I wanted to get the updates for Visio anyhow, so I didn’t get chance to try that.

Ref Link:

Missing Options in Script Generation in SSMS

February 13, 2009 Leave a comment

I was generating scripts in the Management Studio for all objects. Everything looked great; I created my new database with same structure.

Before I let the developer know database was good I decided to run it through ApexSQL Diff to see if there were any issues and sure enough it found issues with few tables.

Looking at it ApexSQL Diff found that three indexes did not get generated properly; in generating the indexes following options were ignored and never scripted out:


Done on SQL Server 2005 SP1 (9.00.2198)

I have tried to do this via the Script Wizard and each Object with same result; I confirmed the database compatibility mode was 2005.

So I though okay maybe because I am running SQL Server 2005 SSMS SP1 thats where the issue is taking place.

So I decided to try it on SQL Server 2005 SSMS SP2 CU9, it came back with more information this time only option that was ignored was:


Done on SQL Server 2005 SP2 CU9 (9.00.3182) and SQL Server 2005 SP2 CU9+Hotfixes (8.00.3310).

I have not used this setting on any index thus far; but if it being used be cautious when transfering objects from one database to another. Run it through tools like ApexSQL Diff or Red Gate Compare or the Microsoft Visual Studio Team System 2008 (Database Edition).

%d bloggers like this: