We're converting our SSRS reports to run against Azure SQL DB. They were previously run against on-prem SQL DB. We ran into an issue where we simply cannot run the reports from Visual Studio. We're getting an very generic error (An error occurred during local report processing). When I simply run a query in a Dataset query window, it returns the data with no issues. It's when I preview the report in visual studio, I get this error. Is anything extra needed to configure this Azure SQL DB?
Thanks.
Congratulations Tony has solved the problem by himself:
"I solved it by using shared datasource instead of a local one."
I help him post it as answer, this can be beneficial to other community members.
Related
I am encountering this error in azure SQL [70527] any suggestions on how to fix this? This is the first time I have encountered this error.
I would appreciate any advice at all, I'm at a loss how to fix this issue, I am not well versed with azure SQL at all
I am assuming you are migrating a database from on premise sql serve to Azure. I suggest you use the migration agent which will highlight all these issues with possible resolution in some cases.
The error code 70527 is related to user login which is highlighted in the following post as well
SQL70527 error in database project
You may have to create the user as per suggestion in the post above using the script method rather than the backup restore.
You can download the migration agent from below link
https://www.microsoft.com/en-us/download/details.aspx?id=53595
I created ms sql database in SSMS 2012. Connected successfully to Azure and trying to deploy db to the cloud.
Encountering following errors:
Please see screen shot
Numerous Usupported property errors — not supported when used as part of a data package
You're likely using a feature not supported in Azure SQL Database. Please refer to this non supported features list to help you pinpoint the problem:
http://msdn.microsoft.com/en-us/library/azure/ff394115.aspx
This happened with me too. In my case ,i changed the schema of a table after creating once for the first time. After deleting that table database deployed correctly. Usually this error occurs when validating schema fails.
Regards
MAnoj Bojja
I have install SSRS in azure using the following instructions (http://msdn.microsoft.com/en-us/library/dn449661.aspx) and all seems to work fine, however when I create a report in report builder 2014 (in this case empty) that includes a Microsoft SQL Azure datasource type I am unable to save the report and get the following error message (even though when I test connection it succeeds).
"The report definition was saved, but one or more errors occurred while setting the report properties"
Reports with standard sql datasources work fine.
I have also tried creating the report using Visual Studio 2013 and get a similar error message.
I have tried this using SQL 2012 and SQL 2014 and get the same error.
Turns out I was running SQL Web edition, you require at least standard to save different types of datasources.
I have created a linked server from one SQL Server 2005 to Another 2005. When I run an update query through the SQL Server Management Studio (SSMS), it runs in under a second. If I run the query through a asp webpage it times out. I ran SQL Profiler to see if I noticed anything as well as the Activity Monitor in SSMS and all I found was that a lock was being created (Wait type LOCK_M_U), but I can't find what is locking it. Any help would be appreciated.
Wade
It could be that the user account that you run under in SSMS and from the ASP page have different permissions on the linked server, which could lead to a difference in which query plans it uses when running your update. See this answer to a more generic question about linked server performance.
The issue seems to be with the ADO activeX component, since I used ASP.Net and it worked flawlessly. Oh well.
Hi My company is deciding for switching its existing application to azure platform (only Sql Part). So we need to upload our db from local to cloud. For migration i came across various tools like
1. cerebrata 's tools
2. SqlAzure Migration wizard
3. Microsoft Sql Data Sync
4. Conventional Script way via management studio.
But all the above tools showed that they have limited capacity. A user cannot work flawlessly on either of the tool.
In cerebrata's tool - the main drawback was its field for Application User Name and Application Key , which my admin havent shared. Also there is manual mapping of fields between azure and local.
Sql Azure Migration wizard - generates scripts and executed too but with lots of error . I was using its version 2.1. Also it very slow. It seems that its a replica of Sql Srvr Mgmt Studio.
Sql Data Sync :- I found it cool as its a MS product but it has limitation too that it only connects with Windows Authentication based local sql server, or you need to explicitly allow the required but. Even after allowing while syncing , I got some Sql Azure Provisioning Error.
4 Sql Srvr Mgmt Studio :- This is most easiest way but requires a lot of manual work to do before actual migration. What i did is that I generated a script of entire db (almost 101123 lines of code for single db) and tried to execute on azure. On the very first time i faced some keyword mismatch error . Finally i removed all line after primary key declaration that With (Padding = Off ....)or something similar and also On Primary then i executed , but still got error on Set Identity Insert On. After doing a lot of hard work in removing unwanted lines waited more than 2 hrs to completed the script remotely, i got no Errors , errors and errors.
So you guys are requested to please suggest me any good alternative stated than above or i am lacking something and can do more with above.
Thanks
Amit Ranjan
I've faced a similar problem recently, running through the options you've listed.
You might give a try to Red-Gate beta for Azure (free for a few months). I found their tools to be quite good for SQL schema and data replication.
Never tried the Azure build myself, though (I migrated tables manually by the time I was told about the offer).