Blog
Case Sensitivity in Microsoft BI Platform
I recently worked out some naming guideline stuff for a customer. A while later I realized that my definitions are really very useful – except that no one ever cared of them. So I had to find a reason why to follow the definitions and I found it in case sensitivity issues.
I did a quick research and created a list about case sensitivity of Microsoft BI products which should figure out that our devs could run into problems if they just lazy re-type column names, etc. We use some generator steps in our development and specially there will be a lot of issues.
Here’s the list about case sensitivity:
| Technology | Case sensitive | Comments |
|---|---|---|
| SQL Server Database | No | Can be activated by changing collationDetails https://msdn.microsoft.com/en-us/library/ms143726.aspx |
| SQL Server Analysis Services | No | Can be activatedDetails http://sqlblog.com/blogs/jamie_thomson/archive/2010/02/15/mind-that-collation-ssas.aspx |
| SQL Server Integration Services | Yes | Identifiers and contents as well (e.g. Lookup or Merge Join Components)Details http://sqlblog.com/blogs/andy_leonard/archive/2010/05/28/ssis-is-case-senstivie.aspx |
| SQL Server Reporting Services | Yes | Identifiers and contents as well https://skamie.wordpress.com/2010/06/19/ssrs-case-sensitive/ |
As you could easily imagine, we had a lot of problems during implementation and the willingness to check the spelling AND the casing of names is increasing from problem to problem.
Would you like to share your thoughts?
Would you like to share your thoughts?
0 Comments