Having issues getting the Format String applied. Running SSDT in VS2013 and deploying to SQL Server 2014.
Settings
Result
Excel also doesn't display the selected format. Is there anything I am missing?
Answer found on technet.
This is because the new cube browser control used in SSDT (unlike the old cube browser used for earlier versions of BIDS/SSAS) does not display the formatted value, it just displays the raw, unformatted value only.
Testing in Excel reveiled format strings being applied.
Source:
http://social.technet.microsoft.com/Forums/en-US/171fa5b0-014b-4a64-a590-9c3d2392b528/ssas-2012-measure-formatting?forum=sqlanalysisservices
The FormatString setting can be viewed properly when you export your SSDT cube browser to Microsoft Excel. The older BIDS (SQL 2008) used to display properly such values, but this feature got lost in newer versions (the latter only display the DataType values without any formatting mask.)
Related
I have an SSRS report that works perfectly in Visual Studio 2017.
But when I deploy it, the deployed report comes back with all the data, ignoring the filters in the WHERE clause. I know it's this because when I remove the WHERE clause from my Visual Studio report, the data matches the deployed report.
This report pings off a shared data source; the dataset is not a shared.
Even a simple WHERE tbl.flag = 'Y' does not seem to do anything to the deployed report.
Why is SSRS not recognizing the entire SQL?
Not really an expert in SSRS, I just make them based off some YT tutorials and deploy them to the link that was given to me, so any advice or links for research are appreciated.
Check the server setting in the report project properties in Visual Studio.
If they look OK then delete the server copy of the report and redeploy.
If the report does not reappear then that proves that the report is either
a. not being deployed (you should see an error in the visual studio output window), or
b. it's being deployed to where you think it should be.
From the web portal you can search for a report by name and it will search all folders on the server so if it did deploy OK, you could find it that way.
I have discovered the issues was some inline comments I had in the SQL. I had some comments above the WHERE clause using dashes, --, explaining the filter. Once I removed it, the report executed correctly.
I was also able to change the comment style to the /* <my comment> */ and it executed correctly. It seems that other style of comments with dashes made the server think everything afterwards was a comment, and therefore not executed.
There is an issue with full-text search in SQL Server 2012 while it works fine in SQL Server 2016.
I have the following sample images showing the output of the similar query which returns data with underscore in 2016 and in other screen it doesn't return any data with underscore and that is in SQL Server 2012.
In SQL 2012
In SQL 2016
Can anyone suggest a solution for this or any reference suggesting the solution for this issue and also the explanation why this kind of behavior is seen in between these SQL Versions.
After working on finding a solution for this issue with full-text search it is identified as the work breaker .dll is been built on different versions of SQL Server with certain special characters as word breakers.
We cannot view the list of word breakers to confirm this as it is built on .dll based architecture and we can only get the paths indicating the .dll file location's. To manually add a character to this word breaker .dll, it can be very complicated and time taking process and will have to do reverse engineering with the .dll's and try to add the above mentioned "underscore" as a word breaker and recreate the .dll.
https://dba.stackexchange.com/questions/50366/sql-server-2012-full-text-search-break-word-underscore
Partial fix with reference to the above URL they were able to get the result by changing the language to Chinese (1028) and we cannot do that as it can create other issues related to synonym search using full-text.
After a recent upgrade from SQL Server 2008 to SQL Server 2012, my Management Studio no longer provides the drop-down boxes of table names or of column names.
Prior to the upgrade, when I started typing the table name (ex: after entering TAP3) a drop-down box would appear providing a list of all tables that began with TAP3. The same applies to the column names.
Now that function no longer works. I have Googled this in general and have checked all of the recommended settings for IntelliSense (not even sure that's what is affecting this!) and haven't found anything to help.
The strange things are that co-workers using the exact same version and tables have no problems with the drop-down boxes. Any help would be appreciated!
I am using visual studio 2008 and reporting service 2008.
I created a .rdl reports. Now I want to convert .rdl to .rdlc. How can I do it?
Good question. According to spec whey should be more or less the same, but in reality they differ wildly depending on version. For instance if I open an RDLC file I created in Visual Studio 2010 in Report Builder 3.0 it works. But if I make a change in my RDL(C) file and try to open it in VS2010 I first get asked if I want to convert it to RDLC 2008 format (yes) and then I get the error message "The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition' which cannot be upgraded."
There is nothing to convert. All you have to do is to rename the file to .rdlc. This converts it from a server report to a client report. The underlying schema is the same, whether it's an .rdl or .rdlc file.
Take a look at FAQ #8 here: http://www.gotreportviewer.com/
I found working with MS support that converting an RDL to RDLC merely by changing the extensions results in a ReportViewer Control HTTPHandler error which is shown with a style of "dsiplay:none". It accuses the developer of not including the HTTPHandler in the web.config, when it is actually in the web.config. Using an rdlc created by VS in that project, then the reportviewer opens just fine and properly displays. MS support and I are still researching what other changes need to be made, but as of now, I can let people know not to drink the MSDN Kool-Aid.
I also tried changing the schemas namespace in the XML file and I got the same report definition cited above.
I'd like to force SQL Management Studio - Import Data - from XLS excel file to read one column as specific data type? It does a type guessing. My first N rows contain decimal data, but some later columns have also characters in there. I know I need to specify IMEX=1 in the connection string to the XLS file, but as far as I know this could be done only if I were using ADO.NET application to do it. (this forces Jet engine to honor registry setting HKML\Software\Microsoft\Jet\4.0\Engines\Excel\ImportMixedTypes which is set to Text).
It could also be done if I had developer/enterprise edition of sql server 2008, and editing DTS package to include the connection string. But I use Express edition that does not allow saving DTS packages - what are my other options? Thanks
Use the OLE DB Provier for Access Database Engine (or Jet depending on version of Excel), click the 'Properties' button to bring up the 'Data Link Properties' dialog, click the 'All' tab and in the list edit the 'Extended Properties' item to add IMEX=1.
Where to get the OLE DB provider? The version for the Access Database Engine, known as ACE, which was released as part of Access2007, can be used to open Jet 4.0 data sources including Excel spreadsheets. It can be downloaded from MSDN as 2007 Office System Driver: Data Connectivity Components. The stated supported operating systems are: Windows 7, Windows Vista, Windows Server 2008, Windows Server 2003 and Windows XP. There could be an equivalent for Access2010 but I'm out of the loop.
Add a first row having text data that you remove from the target table after importing the data.