Amongst many, one of the new exciting feature in SQL Server 2016 is the inclusion of Revolution Analytic popularly known as R or Advanced Analytic. For the seasoned SQL professionals like me R was the 18th letter of the alphabet but not for long. The kid in me that likes new shiny things went digging to figure what this “R” was.
So what is R?
R is the sequel (pun intended) of a language called S developed by some AT&T dudes back in the 90’s which presumably “altered how people analyze, visualize and manipulated data.” R expands on this idea and it’s quite common in the data scientist field. It has very extensive and powerful graphic abilities tightly linked to analytical capabilities.
From SQL Server perspective, incorporation of R allows us to do advanced analysis without having to export the data out of SQL Server and it grows a new breed of data analysts to bring big data analytic to SQL Server.
Oohh and its open source too, so trend knowing attention may be limited.
Knowing that, combined with the love of data, we’ll try to become scientisty with the tools in our hands.
I was in the process of making all things pretty in SharePoint configuration and I got combated with the following error message The search application ‘f8cfe196-b555-4e72-bcbb-cf024cebbc24’ on server <> did not finish loading. View the event logs on the affected server for more information.
As a common practice, “google it” but what’s out there was delete the search service and recreate… that was not an option for me because I had just finished making things pretty so I took the challenge, and it lead me to different places with final destination being WSS_Admin_WPG group. So the fix was pretty simple
- Navigate to Local Users and Groups on your SharePoint Server
- Find the WSS_Admin_WPG group and ensure that you have your Search Service account and your farm account in it.
- Find the WSS_WPG group and do the same.
- Go back to your Search Service application and it’s magically working…
Common occurrences when installing the .Net framework 3.5
Missing KB2966826; KB2966827; KB2966828
If the KB’s exist the article below is very helpful on the resolution
The article from http://www.askvg.com/fix-0x800f0906-and-0x800f081f-error-messages-while-installing-net-framework-3-5-in-windows-8/ details how you can fix the issue but I had a caveat in my encounter.
You look at the DISM error logs and you do see error as described in the article above.
DISM Package Manager: PID=1108 TID=1940 Failed finalizing changes. – CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
But when you look in security updates you don’t see any of the KB’s that support .Net Framework 3.5
Usually the issue is referencing the sxs directory using a UNC path.
Copy the sxs directory to the local server, then run your DISM Powershell command as shown below.
dism /online /enable-feature /featurename:NetFX3 /all /Source:E:\sxs /LimitAccess
I see this error from time to time, usually when you try to create a Power View report from the data connection you get the error that Power View is not support in this edition of reporting services.
Very self explanatory, its the edition of reporting services that was installed on the SharePoint Farm for Integrated mode that’s wrong. The requirements Business Intelligence as environment is SQL Server BI edition or Enterprise edition.
Chances are when Reporting Services Integrated mode was installed, it was installed with SQL Server Standard Edition.
So how do you fix it? You can easily upgrade the edition of SQL Server installed and it will take care of the problem.
While deploying SSIS Packages in SQL Server 2012/2014 you receive the following error
An error occurred in the Microsoft .NET Framework while trying to load assembly id 65536. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE
One of the reasons is because your SSISDB is a participant in AlwaysOn high availability environment.
Ensure that you are deploying your packages to the Primary node, use the Listener connection name if necessary so that you can validate that you are deploying to the right node.
Quick tip, I had a request from one of my customers on how they can make an InfoPath promoted column show up in currency format in SharePoint. The easiest and most straight forward way is to create a calculated column and set the column type to currency. – Done
Last night in my adventure I found a post where someone quit Microsoft BI after encountering “Sorry, something went wrong while loading the model for the item or data source ‘Connection name’. Verify that the connection information is correct and that you have permissions to access the data source.”
To save someone a headache SQL 2014 does not support analysis and visualization of multi-dimensional models using Power view in Excel 2013 it’s primarily supported in SharePoint Mode.