It is saying
ORA-00933: SQL command not properly ended
But I have no idea what I'm doing wrong. Each of these queries run on their own, but not together. What am I doing incorrectly?
In Apex SQL Workshop, you can run only one query at a time. How?
either by keeping only one query in the window and running it alone; then removing it and running another one (also alone)
or, select one query (with a mouse - paint the whole query "blue") and run it (you can click the "Run" button, or press "CTRL + ENTER"). When you have one query selected, you can keep as many other queried there as you want. That's probably a better option. See the screenshot:
If i have understood clearly then do you want get two different report from the SQL quires. I am afraid , is this functionality (running two different quires) separately in the same region would be possible in oracle apex. That could be the reason the apex is throwing error.
Related
Two years ago a SQL expert opened a SSMS and showed all queries as they were happening in real time. That way he saw which SQL statements were running fast and which took some time to be ran. I remember the queries to be displayed in a "CMD" look alike window. I can't remember if new queries were displayed at the top or were they shown at the bottom of the window.
For the past month I have been trying to figure out how he got this working. I looked everywhere in monitor, but I can't find anything similar to what he showed me than.
The results were similar to the "claymore eth miner window" ...
Can someone point me in the direction of getting this?
You can use sp_whoisactive to get the current running queries. It is very useful to see if currently there is blocking, locking, long running statements.
In order to get better picture of what was going on in the past, you can enable the Query Store. There are some predefined reports:
and various statistics and it is user friendly:
Is it possible to stop a running query in the SnowSQL command line tool? Let's say I made a mistake and I tried to run a heavy query.
Control-C, Esc, Q... nothing seems to stop it. The only way seems to be to send a kill command.
I also tried to stop a query when I'm paging but it seems like I'm forced to go through all pages before being able to stop.
Is there any way to stop queries in any of these two situations?
ctrl+c is working fine for me, I executed a simple query
select * from <HUGE TABLE>;
While the results are getting displayed on the command window I fired the ctrl+c
SnowSQL verion : v1.2.5
Operating System : Windows
This cancels the query.
SELECT SYSTEM$CANCEL_QUERY( 'query_id' )
The query ID can be obtained from the Account->History. Many companies do not allow access to account for developers, but can add permissions to allow access to query history.
I was trying to copy and paste some queries and noticed that the paste option is not working. After that I realized that my copy, paste, delete and next line option is not working at all. What will be the reason for this issue.
When you press the Ctrl key, the text editor is looking for a mouse click to "Go to Definition".
Tools>Options>Text Editor>General> Uncheck "Enable mouse click to perform Go To Definition"
(or you can change the modifier key to something you use less often if you want to continue using this feature)
What, exactly, are you trying to copy, and from where? For instance, if you're attempting to copy and paste tables, views or stored procedures (etc) in the Object Explorer, you'll have no luck.
For most of these items, you should be able to right-click, select "Script [Table | View | Stored Procedure ] As > CREATE TO > New Query Editor Window", then run the script.
Unfortunately(?), SSMS isn't as easy going as Microsoft Access, there's definitely a little work involved.
just experienced the same situation in SSMS v18.5!
Also wasn't able to paste/copy code in the Query's Window.
After playing around and restarting the App it wouldn't work.
I did not have issues copying/pasting in all other applications.
Then I found a solution myself by simply thinking about how to "re-init" the engine of Copy/Paste in SSMS:
Go to: Tools | Options | General | Check "Apply Cut or Copy to blank lines when there is no selection".
After applying the "fix" you should be able to copy/paste again! You may reset the checkmark later.
Hope you other guys have the same luck!
Edit: A few hours later the Copy/Paste again was not working and the fix did not work. I found out that a separate instance of Visual Studio had the same copy/paste problem. So it may be either a Windows 10 or .NET problem.
A reboot helped me in that case.
I encountered this problem too, and got a message saying my pc was out of memory. This could be caused by too many apps being open or too many background processes running.
Simply restarting the pc resolved the problem.
We've been successfully using SSRS auto refresh (SQL Server 2008R2) on a variety of clients over the years and never had any problems. Various combinations of Chrome and IE on various OSs (windows XP, 7 and 10) have all been fine. We've just deployed a new report to run in full screen mode on TV screens, and it seems to be PARTIALLY refreshing. The Globals!ExecutionTime displays accurately, but new rows (INSERTs in the source data) in the report's tablix do not show up until the report is manually refreshed. Even more oddly, UPDATEs to the source data seem to make it through the auto refresh process. The problem only seems to occur on these particular clients.
We've set up a report history to help monitor this problem, and it works as expected. In fact it highlights the inconsistency, where newer information is captured in snapshots that were run earlier that the screen autorefresh.
The report execution logs are recording exactly the executions we'd expect to see. The data is just not making it onto the screen.
The report's processing options are:
Always run this report with the most recent data,
Do not cache temporary copies of this report
Any suggestions greatly appreciated :-)
Well we eventually resolved it. The problem turned out to be not exactly as described above. It seems to have been due to unusual combination of several cascading parameters, and a rapidly changing underlying dataset. What would happen, is that:
The SQL behind the cascading parameters would be executed on autorefresh in order to populate each parameter's default values.
During or shortly after this, the source data would change.
Next the final dataset SQL would be executed using the now out-of-date parameter values, and bring back the wrong results.
The solution was to remove four of the five cascading parameters from the report (and the underlying stored procedure). The stored procedure had initially been intended to be widely used and that was the reason for needing all the parameters. Turns out though that it was only used by the report, so as luck would have it we were able to simplify the process.
To the best of my knowledge, I'm correctly importing my MS-SQL data source in the Control Panel (It says successful in green). I'm also pretty sure I'm importing the data correctly into the Windows 7 Publisher app since I can view the data in the DataView:
but when I go to the Layout View or Run Preview, I just get a blank chart:
It works if I use the default SimulatedTable but once I change the data source to my MS-SQL table, I can't get anything to display, no matter what display element I'm trying to use.
I've tried re-importing the data, using a different MS-SQL table, and re-naming the columns to match the SimulatedTable but it doesn't change the result. Can anyone tell me what I'm doing wrong?
Please try one thing, I am just guessing it might work.
Please select one of the Time Preset buttons and see if you see data in that(where there is blank) chart object.
If yes, then while setting up the time navigator object, select an option in drop down box labeled "Default Time Range Preset"
There are some hacks, please do let me know if run into some weirdness. It might not make sense if i try to explain unless you run into that situation.
Cheers,
I ended up giving up on the Windows 7 version of the application and running a virtual instance of Windows 8.1 instead so I could install the Datazen Publisher app for Windows 8.1. It's FAR less buggy.
Not perfect, though.