[EN} BIDS Helper version 1.6.5 released

BIDSHelperSmallLogoTwo days ago (January 7th) new version of BIDS (Business Intelligence Development Studio) Helper has been released /and yesterday Jan. 8th files has been updated/. This fantastic feature is an add-in using for Business Intelligence projects with:

  • Visual Studio 2005 and SQL Server 2005
  • Visual Studio 2008 and SQL Server 2008 and SQL Server 2008 R2
  • Visual Studio 2010 and Visual Studio 2012 for SQL Server 2012

When You get file from CodePlex, unzipping, and installing, You will get access for many features:

  • Analysis Services Multidimensional:

Aggregation Manager Calculation Helpers Column Usage Reports Delete Unused Aggregations Delete Unused Indexes Deploy Aggregation Designs Deploy MDX Script Deploy Perspectives Dimension Data Type Discrepancy Check Dimension Health Check Dimension Optimization Report Duplicate Role Many-to-Many Matrix Compression Measure Group Health Check Non-Default Properties Report Parent-Child Dimension Naturalizer Printer Friendly Aggregations Printer Friendly Dimension Usage Roles Report Similar Aggregations Smart Diff Show Extra Properties Sync Descriptions Test Aggregation Performance Tri-State Perspectives Update Estimated Counts Validate Aggregations Visualize Attribute Lattice

  • Analysis Services Tabular:

 Roles Report Smart Diff Tabular Actions Editor Tabular Display Folders Tabular HideMemberIf Tabular Pre-Build Tabular Sync Descriptions Tabular Translations Editor Tabular Annotation Workaround Unused Columns Report 

  • Integration Services:

Batch Property Update Biml Package Generator Create Fixed Width Columns Deploy SSIS Packages Design Warnings dtsConfig File Formatter Expression and Configuration Highlighter Expression List Fix Relative Paths Non-Default Properties Report Pipeline Component Performance Breakdown Reset GUIDs Smart Diff Sort Project Files Sortable Package Properties Report SSIS Performance Visualization Variables Window Extensions

  • Reporting Services:

 Dataset Usage Reports Delete Dataset Cache Files Smart Diff

  • General:

Enable/Disable features Preferences Version Notification

From add-in’s download page You can choose from few versions:

  • BIDSHelper2012Setup(1.6.5.0).exe | application, 1743K, uploaded Tue – 141 downloads
  • BIDSHelper2012_1_6_5_0.zip | application, 2317K, uploaded Tue – 17 downloads
  • BIDSHelper2008Setup(1.6.5.0).exe | application, 1711K, uploaded Tue – 80 downloads
  • BIDSHelper2008_1_6_5_0.zip | application, 2277K, uploaded Tue – 16 downloads
  • BIDSHelper2005Setup(1.6.5.0).exe | application, 1711K, uploaded Tue – 16 downloads
  • BIDSHelper2005_1_6_5_0.zip | application, 2276K, uploaded Tue – 5 downloads

And when You get Your favorite… let’s play.

[EN] How to DO IT? My Maintenance SUB-Plans doesn’t work.

Last night I discovered on one of my customers systems, that Maintenance Plan doesn’t work. After few hours I received request form customer with printscreen:

image

Pict. 01 | Error with execution of Maintenance Plans.

When we look into message error we get more details:

image

Pict. 02 | Weekly Batch contains multiple plans…

But what is wrong with that? Customer’s idea was: to executing one batch (in this case weekly) with four subplans such: DBCC CHECKDB, REORGANIZE INDEXES, UPDATE STATISTICS and BACKUP (type FULL) for All Systems Databases. All together looks like this:

Captura_MaintenancePlans2005_08

Pict. 03 | One batch, four subplans and errors

The administrator creates exactly the same weekly batch for Users Databases, but it’s one small and important difference:

Captura_MaintenancePlans2005_09

Pict. 04 | Executing “exactly” the same batch for All User Databases.

 

The difference is very clear: they are four plans in first example and one in second. Let’s comparing differences:

image

Pict. 05 | I’ve got You! Right side: System Databases and Leftt side: User Databases.

As we see our maintenance plans are different, and they cannot work the same. Now we have two options: we can change first batch in SSIS or creat the new one (simple and fast option). But be sure that we will not repeat the design error:

image

Pict. 06 | We must remember about second option: Single schedule for ENTIRE PLAN or no schedule

At the end we have two Maintenance Plans, designed and scheduler very similar (only schedule od execution and types od databases are different):

image

Pict. 07 | Comparing the batches.

Think twice (what you need), design (how it shoud work), think one more (how it looks) time and execute (to check).

[EN] How to DO IT? Changing Server Name in SQL Server.

Last week, this week and next week are under my New Labs Development Shadow. Plan is  big for me: some machines for SQL Server, some for SharePoint, some for testing my production environment, some just only for joy. And one of the part of my environment are oriented for SQL Server. Plan is really simple:

All versions of SQL Server (separate by versions and service packs) run on separate virtual machines. All SQL Servers based on Windows Server 2008 R2 Enterprise SP1 x64. Basic environmet is identical for all machines. The differences starting with SQL Server:

  • one machine for SQL Server 2005 SP4
  • four machines with SQL Server 2008 (without and with SP1, SP2, SP3)
  • three machines with SQL Server 2008 R2 (without and with SP1, SP2)
  • two machnes with SQL Server 2012 (with and without SP)

Building ten machines is extremely time consuming. I using cloning machines (soon in other post about it). Because each machine is the clone from another  branch, preparation happened in few steps:

  • step one: master (Windows Server 2008 R2 Enterprise SP1 x64 with all updates)
  • step two: copied to four copies
  • step three: on second copy installed SQL Server 2008 without any updates
  • step four: copied for four copies (without and with SP1, SP2, SP3)
  • step five: each copy are configuring separately

When my virtual machine with SQL Server 2008 SP3 and CU 8 has been configured, I asked my new server: Hello, What’s Your name? So we asking:

1: sp_helpserver
2: SELECT @@servername

And result is completely unexpected:

Captura_HowChangeInstanceName_02

Pict.01 | Result of executing command about server name

Ho, ho, ho. Did You remember phone number for the girl above? Not? Nothing New, You watched for her eyes, you not listen. Why our instance name os so weird? This is NETWORK NAME of Windows Server definied by default Windows Name Generator. Even we changed name in Control panel, our instance (You remember she wasn’t installed from begining. She’s clone). A Nightmare to Remember is remembering instance name with more that… ONE INSTANCE. So, can we rename our instance? If we can saying sweetie or kitty or … for our girl (the real name should be… Cassandra), we can change the name. let’s do it – one more important thing – withour surgery assistance.

So we should go to SSMS (SQL Server Management Studio) and executing statement:

1: sp_dropserver <old_name>;
2: GO
3: sp_addserver <new_name>, local;
4: GO

Executing statement is not all. Next we must restart the instance with command line:

Captura_HowChangeInstanceName_03

Pict.2 | Standard cmd prompt: NET STOP MSSQLSERVER and NET START MSSQLSERVER

After changing Server name, we can ask again: OK, sweetie. What is Your real name?l

Captura_HowChangeInstanceName_04

Pict.3 | New Server Name is visible after all.

ENJOY.