I have some problem with SAP Crystal Report. We have just upgraded the server, to the new server. Since the server did run in tandem with old server, we had to give it another name.
The problem, is that crystal report would not function at all to the new server. It saved the connection to old server at the rpt file, and refuses to change the connection. All properties were grayed out, and cannot be changed to new connection.
So I made a new connection, and wanted to copy the SQL query to the new connection. But when I click on View Command or Edit Command, nothing happened.
Any idea on how to transfer existing rpt to the new server?
I ended up creating dummy server with name as old server. Doesn't need to have same table or anything, just dummy SQL server. The query suddenly works, albeit errors, but I can copy them all to new report
Related
I have made a copy of a server that hosts SQL Server with SSAS for test purposes. I have changed the name of the server so that it does not conflict with the original. It runs on the same network as the original. It processes a series of SSIS jobs that end with a SSAS step to create a cube. To get the SSIS jobs to run correctly, I have renamed the connection strings for all of the jobs so they reference the new name of the test server. However, when I change the server name in the connection manager string, it throws an error in BIDS. It seems to be trying to access the original server despite changing the connection reference. See the screen shot for details of the error. Has anyone run into this? I could reconstruct the step or open the dtsx file ion a text editor, but I wanted to make my changes as simple as possible. Has anyone run into this and what was your fix?
screenshot
Thanks for the reply, I do not have access to the project file for the cube. What I did find is that the problem wasn't the job but the Analysis Services after the clone. I changed the setting for LinkToOtherInstance to 1. I would have preferred not to change the setting becasue now the servers are no longer exactly the same, but it appears to work. The link below was helpful.
http://markwheeler.com/wordpress/?p=175
I just got approved for the Azure SQL Data Warehouse Preview, and just finished "provisioning" my new server and database. I followed a link to a 'Getting Started' page from Microsoft (Get started: Connect ...), and read that the two best (only?) ways of querying the database were through sqlcmd and Visual Studio 2013.
I ignored this advice first, and fired up SSMS, connected to the database, and then tried to open a new query window. I immediately received the following error: 'Unable to apply connection settings. The detailed error message is: 'NoCount' is not a recognized option.' After clicking OK, the query window did open up, but many T-SQL statements did not work such as a simple:
CREATE TABLE dbo.tblTest (acct_id nvarchar(255) NOT NULL)
I would receive a 'Command(s) completed successfully.' message, however no table was created.
Ok, I fired up Visual Studio 2013, connect to my Azure SQL Data Warehouse, and open it up in SQL Server Object Explorer. I right-clicked the specific database, and selected 'New Query', enter the same T-SQL CREATE TABLE statement as above, then hit execute. Once I hit execute, I get the exact same error message as above. This time around I was able to open a new query window at least, but after attempting to execute the query I still get the 'NoCount' is not a recognized option error.
I'm completely new to data warehouses, and still very much a beginner with T-SQL and SQL Server as well. But, I haven't been able to find anything that would explain why I'm receiving these errors, and right now I'm basically at a standstill until I can understand what's going on. Any help is appreciated, thanks.
I've experienced this. Your connection isn't actually recognised as a SQL DW connection. I bet your query window is a .sql file, not a .dsql as it needs to be.
Go back into the Azure portal and use the link to connect using SSDT from there. You should get a connection in the SQL Server Explorer pane which looks different, and when you start a New Query based on it, you should get a .dsql window, not a .sql one.
Have you checked the version of SSDT that you are using? It sounds like you may be on a version prior to 12.0.50623, which doesn't take into account that SET NO COUNT is not supported by SQL Data Warehouse at the moment. Newer versions of SSDT have adjusted for this. We recommend updating SSDT here and then connecting using the SQL Server Object Explorer with the directions in our documentation.
I am running Visual Studio 2015 Enterprise, and what I had to do to get this error resolved was install SSDT October 2015 Preview in Visual Studio. The link I used is: https://msdn.microsoft.com/en-us/library/mt204009.aspx
Prior to installing this, I had the latest released version for VS2015...had to install the Preview to get it to work. Also, it solved the issue where I was not able to see ANY of the tables in the Azure Data Warehouse database - just a couple of views, which made querying difficult (could still get a list of available tables from sys.tables)
I hope this helps somebody!
I'm trying to configure Crystal report to read the connection data from an ODBC, so it can read the required database given the system where it's installed.
However, the .rpt always connects to the server where it was created, ignoring the ODBC configuration (or, at least, the server name).
i've tried updating the connection and changing the ODBC, but still asks for the first server were it was connected.
is there any way to check if the connection is embed or to make the report read the whole connection from the ODBC?
This happens with most of the reports i'm working on (about 100).
I'm using Sap CR 13, and the reports were migrated from CR 8
Thanks!
open CR without a report, go to File, Log On or Off Server and it will open Data Explorer windows. Right there you can delete your old connection(right click on the connection and Delete connection) and leave the new one. Then, when you open the report, it should have the new one.
Another thing you can try is going to Database, Set Database Location... and change the old routed table for the new one.
We have a few 100's of SSIS packages in our environment. Last night we moved our database from one server to another and renamed it. We now need to go into all of packages and change the connection manager to point to the new database server name.
We want to know if there is a way to create a #variablename that we can store our new server name in it (i.e. 'ELITEDB.SIRS-db') in it so we can then put the #variablename into the Connection Manager area. This way if we move servers again in another year we only need to make this change once because the new #variablename will be able to pull the new Server name.DBname.
I hope this makes sense to the masses out there?
If you're working with SSIS 2012, just right-click on the connection and select "Parametrize". Thereafter the connection will be settable with the parameters you create.
access is the front end and sql server 2008 is the backend
i am opening the specific table in access. i have no problem editing data in this table using sql server and then displaying the changes in access; however, when i add a new field in sql server, the changes are not reflected in access.
i am opening the table as a datasheet and it is not showing the new field that i added in access. ive opened and closed the file and still doesn't work
anyone know what's going on here?
You might need to refresh the SQL Server table in Access using Linked Table Manager.
I cannot add comment but I like to add...
since it irritates me.
It is the same story not only in MS Access, it is the same in SSMS (MS SQL Server Management Studio, even from the latest MS SQL Server 2008 R2) with its own "native" mdf databases and tables from it.
If to change the content of a table through another window / tab or instance of SSMS (by TSQL, or by interactive editing) then the content shown in already opened for interactive editing table is not updated, though it is updated by non-documented Ctrl+R.
And it is not available in GUI of SSMS (no menu entry, no button, etc.)!!!
Any browser/webapp can be easily configured to update the content but not MS desktop IDE GUI!!!
But if to ALTER TABLE, for ex., to add a column, then already opened tab with table (SSMS) cannot reflect the changes (cannot show altered table, for ex., with added column) even by pressing Ctrl+R.
It is necessary to close tab (window) with table and reopen it
(right-clicking on table in SSMS ObjectExplorer --> Edit tio 200 rows)!!!
I remeber I opened a bug in Microsoft Connect feedback on it and it was closed as this was a feature "by design"!
Still IMHO it is a bug and requires brute force (/ugly GUI actions) to bypass it
This SO Q&A seems to cover similar territory.