We have just done an upgrade of SSRS from 2012 to 2016 and now something odd is happening, some not all of our reports are now showing dates in a US format when previously they were in a UK format (as we wanted). It's obviously a default but I can't seem to find where, the machine is set to UK time and location.
Does anyone know where this value is or what I should check?
Thanks,
Nic
The date format in Preview mode in Report Designer is determined by the culture of the operating system, while the date format in the report manager depends on the culture of the browser.
have a look on below post
SSRS - Date Format
Related
I am using Web Intelligence for reporting however, the SQL script i use runs fine within Oracle where it displays the date and time of a column.
But when i run this report through web intelligence and then export, it only displays the date.
I am probably missing something incredibly easy but I cant see it.
All you should have to do is explicitly set a format rather than leaving it as the default format.
And I get this...
Local Mode Reporting Services has limitations compared to remote Report Server version but it is needed for many scenarios with hosted SMBs since SQL Server 2012 Web Edition is much more cost effective for small companies and it only permits local mode reports.
However, if I want to use dynamic values from the web page (such as parameter values) I cannot reference them from the RDLC and therefore cannot access them. I can update the dataset that the Report returns by passing values to "ReportViewer1.LocalReport.SetParameters..." but these values aren't available in the report (they shape the data returned but are not in themselves available).
For example, if parameters included the date bounds of a query I could not get the "StartDate" parameter expressed as a heading via an expression. Of course, I can get the Date of the first record returned and show that via an expression, but I might have queried from June 1 and the first item might be dated June 3. My report would be better if I could label the query range "June 1" in my header. I could also nest the report in a web page and handle the labeling that way but then my PDF/Excel output would still be displeasing.
The only other thing that I can think of (that seems quite inelegant) is to add metadata tables to the project database to query for the express purpose of returning values to garnish the report.
Am I missing something?
I have a SQL Server 2008 database with an Access front-end. My problem is that Access does not recognise SQL Server's dates as they are in a different format.
SQL Server-s format is YYYY-MM-DD
Access' format is DD-MM-YYYY
When the date is displayed in a text-box, it is displayed as a string (without the little calendar icon next to it).
Is there anyway I can configure my Access front-end so that it recognises SQL Server's dates?
Cheers.
If you are storing the dates in SQL server as the data type “Date” or “Date2” try changing them to “DateTime” I had this problem linking data from SQL server 2008R2 to access 97, access did not see it as a date and treated it like text
The Microsoft SQL Server Migration Assistant for Access does move the dates over as a Date format. The problem the user has encountered is with a Driver. Microsoft has a new DLL that must be put on a client workstation (or server in the case of Citrix).
Once that is done, all the dates in MS Access will work properly.
My lastest experience with Access 2010 was exactly the same as Access 2003. It required a DLL.
From there, investigate using a DNS-Less connection string.
I just ran in to this, thanks everyone for your input.
I'm also developing an Access UI for a SQL Server backend (Access 2010/SQL Server 2014) and just encountered this problem. The Date datatype takes 3 bytes of storage, and since I didn't need a time component, that's what I wanted. Personally I'm using SmallDateTime, it takes 4 bytes compared to DateTime's 8. There's also DateTime2 that takes 6-8 bytes.
I created a four field table using each of the date datatypes to experiment with input formats, I think SmallDateTime will do the trick for me.
I have a report that has ~1k columns and ~17k rows and I'm trying to render it to Excel 2007 with SSRS 2008 R2 Nov CTP.
SSRS team members have mentioned in multiple places that Excel 2007 format is included in 2008 R2, for instance:
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/69545568-73cb-4f4c-8f35-44472ba6d013
Now, it's certainly possible that it just hasn't made it into the product yet (at least as of Nov CTP), and if that's the case, that would be good to know, too (and ideally when it would be in the product).
The repro report and data (along with attempts showing the existing interface still does Excel 2003 format) are attached to the bottom of this blog post, FWIW:
http://cid-456117cf53a42144.spaces.live.com/default.aspx
Unfortunately, it looks like I was misinterpreting Jin Chen's answer ("Here, has good news, we have improved the ability in SQL Server Reporting Services 2008 R2") - there was an answer later by another member of SSRS that states that 2008 R2 will not support xlsx / Excel 2007 output:
http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/87cfd5d4-ea3c-4250-aab8-a1a3dffa3241
As far as a full featured Excel 2007 xlsx renderer, it is definitely on our list to build but it will be post SSRS 2008 R2.
So, maybe it was in R2 but got cut, but either way, it doesn't appear to be an option now.
For those who might be in a similar situation that run across this question on SO, if programmatically generated the spreadsheet is an option for you, I would recommend EPPlus.
http://epplus.codeplex.com/
Excel 2007-2010 format (Office Open XML) is the default rendering format in SQL Server 2012
http://technet.microsoft.com/en-us/library/dd255234.aspx
We store our date/time information in UTC format on our SQL Server.
When using SQL Reporting Services, we'd like to display this data in the time zone of the client workstation, but it appears that using an expression like;
System.TimeZone.CurrentTimeZone.ToLocalTime(Fields!DateStarted.Value)
... converts into the time zone of the server, not of the client workstation?
Is there any way of performing this conversion locally, or passing the local time zone to the server for conversion?
Thanks in advance
Matt
If your reports are standalone I can't see other option than add timezone report parameter.
But if you using reports inside web application, you can Determine Timezone from Request Variables with JavaScript and send time zone value back in hidden fields, urlparameter or postback.
You can also add timezone to user registration info (or figure it out from Country and City fields).
Also you may try Target Your Visitors Using GeoIP and .NET.