Use SP1 for integrating with the BI features of SQL with SPS 2013.

Enjoy

Download it from https://www.microsoft.com/download/en/details.aspx?id=29066

Check out the launch event in sqlserverlaunch.com

Enjoy.

Here is the set of screenshots that explain the demo of creating and running a cleansing project and a matching project:

DQS Client application

The knowledge base

The knowledge base contains a single domain (a single field – the firstname). The domain also contains a single matching rule, the rule says that two records should be considered as identical when the firstname fields contains “similar” values.

We can now create a Data Quality Project – First a Data Cleansing Project

After running the project against AdventureWorksDWDenali (with 3 firstnames in DimCustomer manually altered) we can see the results of the cleansing and the corrections of the process:

We can now export the results:

We can now create and run another a second data quality project for matching and merging:

The first step is the matching process:

The second phase is the survivor process:

in this process you can see the matched records (the records with similar Firstnames according to the matching rule of our knowledge base).

And finally export the matched records:

So these screenshots hopefully will give a glimpse in the Data Quality Services client tools for SQL Server 2012.

Unfortunately the low screen resolution for the demo (1024/768) is not suitable for these client tools – the screen of the DQS client apps is not resizable – so it was impossible to present the demo in this resolution.

Regards,

Nikos

Read what’s new @
https://msdn.microsoft.com/en-us/library/bb510421%28v=SQL.110%29.aspx

• Excel Services Web Service API
• Excel Services REST API
• Excel Web Access web part.
• JSOM

With JSOM, not only can you access the deployed excel in ECS, but also interact with it via JavaScript. For instance you may “attach” an event handler in a range change event on one EWA web part and change the excel in another EWA. Thus making interactive mash-ups with many EWA web parts a reality.

Have a look at a nice blog post of Joseph Chirilov here, and the technet post with the official definition here.

However there is another option – also suitable for SQL Server.

You may use the msmdpump.dll as the conduit for your communication. Just create a web site the “exposes” this dll and use a connection string  (from your office client not a from a browser) like this /msmdpump.dll">https://<SSASMACHINE>/msmdpump.dll .

Here it the process (IIS 7 or higher)

• Create a new site
• Copy the msmdpump.dll in the site. Typically located under C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\bin\isapi
• Add a Script Map in this site with the DLL, name the map as you please –my option is typically olap. Click on the site, double click the “Handler Mapping” icon and select “Add script map…” from the actions at the top left corner
  
• Click OK and Yes when prompted.
• Now you have the option to use the anonymous access to this web site and impersonate any valid user in the SSAS or just keep the windows integrated authentication behavior. The first is a wide open hole in the security – use it only when no other option can work – it is not recommended.

It’s pretty easy to do and it can give accessibility to office clients outside the SSAS windows authentication territory. Particularly useful when business people would like to put their hands on your dev/test environment to test cube data.

I recently faced a situation where the customer had the Lat & Long coordinates of the spots which should be plotted in a map. In order to convert lat & long in Geography type use the following T-SQL:

geography::STPointFromText('POINT(' + CAST([Longitude] AS VARCHAR(10)) + ' ' +
CAST([Latitude] AS VARCHAR(10)) + ')', 4326)

Then you have the option of using the Bing maps in your SSRS reports.

Go to Sharepoint 2010 Management Shell

and use the following cmdlets:

$myservice= Get-SPServiceInstance | where {$_.TypeName -eq "put the service name here"}
$myservice.Service.ProcessIdentity.CurrentIdentityType = 0
$myservice.Service.ProcessIdentity.Update()

Note that you can see the list with the available service names by executing the Get-SPServiceInstance cmdlet.