I'm sure I'm missing something obvious here but I've been searching for half an hour to no avail. In Visual Studio, if I right click on Report and select Add new report then I can do things like select the data source, and input a SQL query. If I want to (for example) change the SQL query of an existing report, how do I do this? Surely I don't have to delete & recreate the report?
You cannot reopen the wizard that you used to initially create the report (or chart). It's a one time wizard that generates a report that you have to manually tweak afterward.
The good news is that it shouldn't take too much effort to change simple things on the report you have. There are lots of examples on SO about how to change the query/expressions or anything else you need to modify.
I faced the same issue when I wanted to change my query and add a new field. A workaround is to manually modify the rdl file:
Righ click on your report (on the solution explorer)
View code
Paste your new query within the < CommandText >< /CommandText >
Add a new < Field >< /Field > in the list
I have an existing stored procedure that I modified to return one more column. I need to get that new column into the existing SSRS report. The report is simple but I want to avoid recreating the whole report if possible. Thank you.
In DataSet properties, go to the "Query" tab. Press the "Refresh Fields" button, and click OK. Save the report. When you go to the "Fields" tab of DataSet properties, the new column should appear.
(This is for Visual Studio 2013. For other versions, the UI may be slightly different, but the basic approach still applies.)
The easiest way to edit the current report, most places I have worked have some type of file control like TFS. Another option is to download the rdl file off the server and edit it.
You have the dataset collection created for this , Edit that ( Ctrl + L ) add the new column name >> Save and refresh
We are using the Crystal Report viewer (XI I believe but we can upgrade) with a VFP front end.
Is there some way to dynamically set the parameter default value at run time? For example, If the user is viewing an invoice and they try to run a report, I would like it to automatically default to the current invoice. As it stands right now, they have to type in the invoice number even though they already have the actual invoice already open.
If not, is there a better viewer available that we could use to accomplish this goal?
I currently use VFP with Crystal Reports in Accountmate SQL (AMSQL). AMSQL has its own blackbox code to do what you are asking so I can't give details on how it is done, but I do set parameters dynamicaly (e.g. invoice#) and Crystal generates a report based on the parameters sent.
I know you can accomplish this in your case by creating a Crystal Reports object in VFP, thereby exposing Crystal properties, events and methods to VFP. Craig Bernston has a good article on what you are looking for at: http://www.craigberntson.com/docs/integratingcr.pdf
I am attempting to create a Stored Procedure for a newly created database. However the SSMS intellisense does not recognize more than half of the tables which have been created.
For example whilst in the left hand column under tables I have a table dbo.Room, when I type "dbo." in the new query window, that table is not listed, in fact only 17 out of 37 tables are listed.
I can see no difference between the tables listed by intellisense and those not. If I manually type dbo.Room, it is underlined, with an error of
Invalid Object Name 'dbo.Room'..
Have I missed something in setting up the tables?
UPDATE: I have tried refresh of the tables list (several times)
Try:
Edit -> IntelliSense -> Refresh Local Cache
This should refresh the data cached by Intellisense to provide typeahead support and pre-execution error detection.
NOTE: Your cursor must be in the query editor for the IntelliSense menu to be visible.
Make sure that the selected DB is the one where the table is. I was running the Script on Master. In my case, I had to switch to hr_db.
Rookie mistake but, could help someone.
Ctrl + Shift + R refreshes intellisense in management studio 2008 as well.
once you create a new SQL Server object, your newly created object does not get updated in the IntelliSence Local Cache and due to this, it shows red line underneath that object. So you just need to refresh SSMS IntelliSence Local Cache and once you refresh it, IntelliSence will automatically add newly created object in the cache and the red line will disappear. try this
Edit -> IntelliSense -> Refresh Local Cache or Ctrl + Shift + R
In my case, the IntelliSense cache was listing object information for an entirely different database. If I clicked the "New Query" button in SSMS, it would open a query to my default catalog on the server and that query editor would always only use that database. Refreshing the cache didn't change anything. Restarting SSMS didn't change anything. Changing the database didn't change anything.
I ended up creating a query by right-clicking on the database I actually wanted to use and choosing "New Query" from that context menu. Now SSMS uses the correct objects for IntelliSense.
Are you certain that the table in question exists?
Have you refreshed the table view in the Object Explorer? This can be done by right clicking the "tables" folder and pressing the F5 key.
You may also need to reresh the Intellisense cache.
This can be done by following the menu route: Edit -> IntelliSense -> Refresh Local Cache
The solution is:
Click menu Query,
then click 'Change Database'.
Select your appropriate database name.
That's it.
Same problem with me when I used this syntax problem solved.
Syntax:
Use [YourDatabaseName]
Your Query Here
Even after installing SP3 to SQL Server 2008 Enterprise this is still an "issue." Ctrl+Shift+R like everyone has been saying solved this problem for me.
In azure data studio press "cmd+shift+p" and type "intellisense", then you will see an option to refresh intellisense cache.
did you try: right click the database, and click "refresh"
I realize this question has already been answered, however, I had a different solution:
If you are writing a script where you drop the tables without recreating them, those tables will show as missing if you try to reference them later on.
Note: This isn't going to happen with a script that is constantly ran, but sometimes it's easier to have a script with queries to reerence than to type them everytime.
Solved for SSMS 2016.
Had a similar problem, but Intellisense was not in Edit menu.
What seemed to fix it was turning Intellisens on and off, right click on the SQL editor and click 'Intellisense Enabled'. Right click again on 'Intellisense Enabled' to turn it back on again. Ctr Q, I also does this.
This solved the problem, and also I know get the Intellisense on the Edit menu.
I just had to close SMSS and reopen it. I tried Refresh Local Cache and that didn't work.
I ran into the problem with :
ODBC and SQL-Server-Authentication in ODBC
and
Firedac-Connection
Solution :
I had to set the Param MetaDefSchema to sqlserver username :
FDConnection1.Params.AddPair('MetaDefSchema', self.FDConnection1.Params.UserName);
The wikidoc sais :
MetaDefSchema=Default schema name. The Design time code >>excludes<< !! the schema name from the object SQL-Server-Authenticatoinname if it is equal to MetaDefSchema.
without setting, the automatic coder creates :
dbname.username.tablename -> invalid object name
With setting MetaDefSchema to sqlserver-username :
dbname.tablename -> works !
See also the embarcadero-doc at :
http://docwiki.embarcadero.com/RADStudio/Rio/en/Connect_to_Microsoft_SQL_Server_(FireDAC)
Hope, it helps someone else..
regards, Lutz
Don't forget to create your migrations after writing the models
For me I had rename from
[Database_LS].[schema].[TableView]
to
[Database_LS].[Database].[schema].[TableView]
I was working on Azure SQL Server. For storing the data I used table values param
like
DECLARE #INTERMEDIATE_TABLE3 TABLE {
x int;
}
I discovered the error in writing on the queries
SELECT
*
FROM
[#INTERMEDIATE_TABLE3]
WHERE
[#INTERMEDIATE_TABLE3].[ConsentDefinitionId] = 3
While querying the columns, it's okay to wrap it with braces like [#INTERMEDIATE_TABLE3].[ConsentDefinitionId] but when referring to just the table valued param, there should be no params. So it should be used as #INTERMEDIATE_TABLE3
So the code now must be changed to
SELECT
*
FROM
#INTERMEDIATE_TABLE3
WHERE
[#INTERMEDIATE_TABLE3].[ConsentDefinitionId] = 3
In my case, I was trying to alter a stored procedure that didn't exist in the database, after creating it and refreshing local cache, it worked
I would like to edit data directly from result grid in ssms. eg:
When I execute SELECT TOP 10 * FROM some_table, I want to edit data directly from result grid.
I don't want to open some_table and edit from there.
I know that result grid is read-only, but maybe someone written addin for it.
You can't edit the data from within the result grid. You'd have to go via the "open table" route if you want to edit the data manually instead of using UPDATE/INSERT SQL statements.
Is there a reason you specifically want to use the result grid instead?
You can specify a query when you go via open table to limit the results if that's your reason? There's a "Show SQL Pane" button in the top toolbar you need to select (square box with "SQL" written in it).
I have very large database (70+ GB) with so many tables.
I'm using Red Gate's SQL refactor for intellisense and few other things.
It's so boring to type in update sql statements every time I need to change single field.
It also takes some time to find that table in the Object explorer.
Intellisense doesn't work when I use "Show SQL Pane".
I'm new to SQL Server and have used the Oracle product 'PL/SQL developer' by All Round Automations at a previous job... It would allow you to do a SELECT in the query window and then simply add "FOR UPDATE" to the end of your refined SQL SELECT and 'ta-da' you can now edit the results in a nice grid. No need to Open Table View, click the SQL button, paste in the SQL you you have been working on and then hit execute ;)
EMS SQL Manager for SQL Server allows to update data directly inside a results grid.
This tool is boring for typing new requests (poor intellisense and error management) but fine for this. I always have the two tools opened.
If you right click on the table and choose edit top 200 records, it produces a result screen with an query.
Add to this your query and then you can edit the records in the result screen.
Also you can change the 200 to a number you want (2000).
The "results" pane is not just results.
Results in text
Assorted time and IO statistics
Estimated and actual execution plans
Row counts, Error messages, PRINT output
etc
This is why they are separate.
Feel free to write your own add-in :-) Or here
SQL Server ISN'T Access!
When you run a query and get the results - thats exactly what you are doing, reading the data, not opening the table for editing. Can you imagine the necessary transactional control around allowing the results window to be edited? The locking would probably grind SQL to a halt - I hope no-one ever writes that kind of add-in!