Context: I'm running some simple queries in Azure Data Studio to query and manipulate data in a local instance of SQL Server 2019.
Question: When I query the table via "Select", the Run button is accessible. As soon as I Truncate the table, the Run button dims & is no longer accessible --__-- Why!? Once the button dims seems I'm unable to execute any other queries in the same query window afterwards. SMH.
Kinda ridiculous that I need to even post this question given how simple these 2 queries are. I expect this button to be easily accessible, similarly to SQL Server Management studio. I read through the docs and dont see anything about this button dimming issue. ADS is built with similar components to VSC so experience or knowledge in that tool may help. Can someone please share any tips/tricks they know on how to fix this issue?
https://learn.microsoft.com/en-us/sql/azure-data-studio/quickstart-sql-server?view=sql-server-ver15
Related
I am going to use reusable mapping in odi 12c, but there is a problem. When ever I drag and drop a table into the environment, it gives me this error:
No object could be dropped on the diagram possibly because the chosen technologies in the "Create As" dialog were incorrect. Please, try again choosing a different technology.
I got confused and I do not know what is wrong because before that I was doing the same thing but suddenly this error pops out.
I was going to develop simple reusable mapping to save that for using in my other mapping.
I got the same error message. I couldn't drag and drop any of my tables - regardless of their source.
I did not find any solution except to delete my old mapping and create a new one.
Closing the ODI and launching again should help as a workaround for this error.
Use the command:
odi -clean -initialize
This will clear the cache and launch ODI and it should negate the error until next time.
I installed Talend last month, and no component can be deleted, as shown below:
No job is running, and this happens to all jobs. I cannot do modification at all.
How to solve this issue?
Case
The context menu in Talend is very inconsistent. By no means all actions are available there all the time. You also need to know specific menus or key commands.
Solution
Row iterators
For this case there are two approaches:
Click row1, then hit Del on your keyboard
Re-route the little black dot at the I with drag and drop to another components input and you are set.
Components
The same here, just click on it and hit Del.
NOTE: If you have further issues with the jobs, please open specific questions to those issues.
If you want to delete a component / row(connecting line between components) , please select the component/row and click on the delete button on the keyboard.
If you are unable to edit any of the jobs, then it points to an access related issue.
If you are using svn to save the jobs, it could be an svn access issue.
If you are using remote connection in an enterprise version, it could be that you no longer have access to the specific project
Here is in interesting one.
I have a Crystal Report that uses a single Microsoft Access 2007 table. The data in the table is updated at run time based on criteria from a list box.
If I select one entry from my list it updates the data and shows in the report. If I select and different entry is shows the data the old data. If i select that report enough times it will eventually show the new data.
The data in the access data base is updated as I checked manually
My problem is that there seems to be a delay in between the data updating and the report showing the new data.
Is there anyway to reduce this delay or get my program to wait until access has finished updating ?
Here's some ideas:
If you're mixing cr-xi with VS2010, and have no real reason to do so, then uninstall xi and install the new libraries for VS2010. I had issues mixing cr-xi with VS2010.
There's an option to save data with report. Make sure that's turned off. If it already was, turn it on, run the report, then turn it off again.
You can try rpt.Refresh(), right before crystalReportViewer1.ReportSource = rpt.
This page had some ideas, including the last one I listed.
This may be a simple fix and maybe I'm missing something obvious, but when I split my DB it wasn't entirely finished, and there have been modifications requested which require me to edit my backend.
How come it's not the same GUI layout (exactly)? Tables open in "windows" within Access, and when maximized, cannot be closed, etc. It's annoying as hell as I can't close my table to deal with its relations. I can only get to design view by finding it in the Tables list and RightClick->Design instead of on the bar above the tables, etc.
Is there a setting somewhere that caused these minor GUI changes when I split the DB? How do I put it back, as it's bugging me greatly; slowing down modifications by a lot.
EDIT: It seems that the "tab windows" option was removed for the backend for some reason..
Appearance of the windows in MS Access 2012 is controlled by the Options settings:
File->Options->Current Database under Document Windows Options
I'm running SSRS 08. My query has four parameters (all varchars). I can run the query through management studio and it runs in under 10sec. I get the same performance if I run the query in Visual Studio's query designer.
However...if I try to preview the report or actually run the report once it's deployed the actual report sometimes takes more than 5 minutes. I ran a trace and the query seems to be in/out of the SQL server side quickly. How can I find where/why I'm loosing this performance? I've tried/checked so far the following:
No images are referenced in the report
No grouping/sorting outside of the stored procedure
Since it's a straight forward report I rebuilt it with same result (to check if it's not an issue of a corrupted report).
ran SQL trace when I executed the report to make sure the query did not have issues
Based on some suggestions before I rewrote the query to use variables instead of parameters like so
-- ...
-- Note: #Parameter is a varchar(40)
-- ...
declare #Var as varchar(40)
set #var=#parameter
select * from table where fieldvalue=#var
Ran the trace and it's not an issue on the query side.
I had the report html output trouble on report retrieving 32000 lines. In my case I had to activate “Interactive Paging” to allow user see first page and able to generate Excel file. The pro is that first page appears fast and user can generate export to Excel or PDF, the cons is that user can scroll only current page. If user wants to see more content he\she must use navigation buttons above the grid. In my case user accepted this behavior because the export to Excel was more important.
To activate “Interactive Paging” you must click on the free area in the report pane and change property “InteractiveSize”\ “Height” on the report level in Properties pane. Set this property to different from 0. I set to 8.5 inches in my case. Also ensure that you unchecked “Keep together on one page if possible” property on the Tablix level (right click on the Tablix, then “Tablix Properties”, then “General”\ “Page Break Options”).
I was troubleshooting a similar issue a while ago and it turned out to be related to the browser I was using to view the report. If the report returns a lot of data to the screen consider splitting it into multiple pages if it is not already configured that way.
Why Does Business Intelligence Studio Load Reports Faster than the Report Server
I think I may have found my answer on a social.msdn.microsoft.com thread
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/1e34dc76-4d78-4376-89b0-7c381ed82726/
I unchecked the "Keep together" setting and it now actually previews coming from the server and I can export the report. Much improvement