1. Full Page view of Analytic Grid is not showing grid headers.

2. Full Page view of Analytic chart is cutting legends.

3. Legends are not showing if resolution is 1024x768(Ipad 2 resolution).

4. If there is gap for items in x-axis the drill down is not working correctly. Example if we are showing weekly trend of full year in chart and week labels are skipping in x-axis then drill down take you to wrong dates.

Create Table dbo.Employee
 (
 EmployeeID Int, 
 FirstName Varchar(30) 
 );
 
 Create Sequence dbo.EmpIDSeq
 As Int Start with 1 increment by 1;
 
 Insert Into Employee(EmployeeID,FirstName)
 values
 (next value for dbo.EmpIDSeq,'John'),
 (next value for dbo.EmpIDSeq,'Mike');
 
 Select * from Employee;

You can create the same using Managemet Studio UI - Database/Programmability/Sequences.

If you have to hide something(textbox,label) while normal rendering of report ,but you want that item(textbox,label) in print or while exporting to PDF,Excel then below is the expression to control it.

=iif(Globals!RenderFormat.IsInteractive=TRUE,TRUE,FALSE).

Here I will talk about installing the DQS component on a named instance of SQLServer and especially on the PowerPivot instance.

Well the trick remains the same, you create an alias on the server where you are installing the DQS component and point it to the named instance. This will create the DQS database on the directed instance of SQL Server.

So if you are installing the the component on the lets say MyInstance of MyServer your alias will look like below.

With PoweverPivot installation you just need to change the Instancename to PowerPivot. But the first important thing to remeber is that the PowerPivot option does not allow you to select DQS component as DB engine option, hence you will need a default instance or named instance to be installed as well to have the DQS files on the server.

What this mean is if you change the InstanceID of your installation during the setup of SQL Server, it will not allow you to install the DQS throwing an error that it was not able to connect to the specified server. Youc can learn more about it from here.

https://msdn.microsoft.com/en-us/library/hh231682.aspx 

Well what do you do then, do you remove and reinstall the SQL Server ?

If you happen to be one of them liek me who has changed the instanceID of your default installation then you can use the following workaround to recify the same.

The DQSInstaller.exe  uses the combination of the servername and the InstanceID to install the DQS components.

For example if you are using MYServer as the server name and InstanceID as MSSQSSERVER12 then it will search for MyServer\MSSQLSERVER12.

What you can do to workaround this is create an alias with the name as MyServer\MSSQLSERVER12 and pointing to the default instance ie. just the server name. A sample is shown below.

 Note that you will have to enable the TCP/IP protocol for bothe the client and the server next.

I had the SQL Server 64 bit version installed and the DQSInstaller.exe is a 64bit code so creating an alias for only the 64-bit client is fine. I am not sure if the 32bit version of the SQL Server will have 32 bit DQSinstaller on it...but nevertheless you can then create the alias of the 32-bit clietn as well.

When you start the new installation, after a few screens of setup suport files and providing the key  and accepting terms you get to see the below screen.

To install DQS you can either choose the first option to specify the features and components you want to install or you can select the last option which will install all the features. Note that while you can choose the second option and install a Database engine along with it, but that option does not provide you DQS component feature selection option.

If you want to install a PowerPivot instance installation on your machine and want to use that instance as the DQS server instead of the default instance for some reason, you will still have to install a default instance or a named instance (But not without a trick, check the end of blog for details) of DB engine using either the 1st or the 3rd option below. We will talk about this in detail a little later in the blog.

For now lets assume you choose the first option.

Next as you can see in the below screenshot the DQS Client comes as a shared component in the SQL Server Install media while the DQS services is listed under the DB engine feature. Choose both of them and then click thorough the next screens with the standard steps and complete the installation. Note that even though the installation is complete the DQS Server is not yet installed on your instance, the setup actually just copies the DQS files on the SQL path.

 Once the installation is complete you will see the following new subfolder inside the Microsoft SQL Server 2012 Parent folder in the Start Menu. The subfolder contains two items, 1) the Client 2) Shortcut to Server installation file, if you click on the Client at this point and try to connect to the server engine you just installed, you will get an error saying DQS is not installed on this server.

To install the server click on the Data Quality Server Installer Item  which will launch a command prompt executing the DQSInstaller.exe from the Binn path of SQL Server install location, with elevated permissions to install the DQS server components for you,this includes the installation of 3 DQS databases on your SQL Engine.

You can now connect to the DQS Server using the client.

All the steps mentioned above go fine if you are installing the DQS on the default instance of the SQL server without making any changes.

Lets say you now have 2 different requirements.

1. Installing the DQS on default instance of SQL server with a different Instance ID. Check the following post for the same.

 https://blogs.technet.com/b/gdcomdbbi/archive/2012/04/03/installing-dqs-on-a-default-instance-with-different-instance-name-and-instance-id.aspx

2. Installing the DQS on a named instance or PowerPivot Instance of SQL Server. Check the following instance for the same.

 https://blogs.technet.com/b/gdcomdbbi/archive/2012/04/03/installing-dqs-on-a-named-instance-of-sql-server-2012.aspx

The DQSInstaller does not yet provide any option to direct the install to a particualr server or instance...may be something which users may desire in future also it does not provide any configuration option for the installation, nor any GUI at this stage, another item to the desired list. Whether this type of installation is officaily supported or not is something to be checked.

SqlPackage.exe can be used along with publish profile to publish database in different environments.

Here is how my publish database profile looks like.

On execute the following command line, it will publish your database to the target server mentioned in the profile.

"C:\Program Files (x86)\Microsoft SQL Server\110\DAC\bin\SqlPackage.exe" /pr:"<Path>\SampleDB.publish.xml"

/sf:"<Path>\SampleDB\SampleDB\bin\Debug\SampleDB.dacpac" /a:Publish

If you make any changes to your database project a new build should be generated. 

When you open an existing VS 2010 database project you will be prompted to upgrade the project to SSDT type. You can also launch the same wizard by right clicking on the project and selecting "Convert to SQL Server Database project..."

Post upgrade, let's have a look at the property page again.

Your existing VS 2010 database project has been converted to SSDT project. You can verify the conversion log for any errors.

Done!!!

In order to save these publish settings and add it to the current solution, check "Add profile to project". You can have multiple profiles added to the project.

Once all options are specified...hit Publish and it will deploy the database project to target server!!!