Before, I used the Query Editor to make some query on my Azure DB, but since some days, it's not working anymore.
Databases are on an SQL Database Server on my Azure Subscription.
To query or modify columns / tables I use Query Editor on portal.azure.com
When we open a new query editor with SSMS, it shows us: disconnect:
And after a while, it will try to connect to the database:
Sometimes, I also have the same error. The query editor has opened for a long time and didn't use it. I reconnect the database and open a new query editor, it will works ok. As you said, you've juste tryied to reproduce and now it's working. So I think the reason is the connection lost or timeout.
Hope this helps.
Related
Dbeaver does not recognize tables written in SQL scripts, however the schema explorer seems to work fine and still shows correct schema and table information. This started occurring after my machine shut off unexpectedly. I am new to dbeaver, how do I resolve this? From a brief google search I can only seem to find other people having the opposite issue. I have already tried disconnecting and reconnecting to the database to no avail.
Recently I run into a scenario, where
I created a table in a database.
Refreshed the tables in Object explorer
Table appeared in the list
I used the query 'select * from sys.tables' and selected the database in dropdown list
Executed the query
Table NOT in the list
We are using SQL server 2008 R2 and this issue is observed on our clients machine. Sadly, I don't know much about the history of the database.
Has anyone seen this issue before. Any little help will be greatly appreciated
Finally figured out the issue..
Issue is because we are using remote connections. It seems SQL query editor will remember the connection. So query editor is using one connection and Object explorer is using a different connection. They both are not pointing to the same server.
So when we created a table using SSMS, then we can see the table created, but not the same when used with query editor. As both the servers has same databases we always thought that it's the same server.
To change the connection of query editor, Right click on the sql query editor -> Connections -> Change connection.
With this we changed the connection of the query editor. And now both Object explorer and query editor are in sync, and we can see the table that is created.
Happy ending!!
#Mortb and #Manngo, once again many thanks for your contribution..
I'm using Oracle SQL Developer 3.0.04. Trying to connect to a remote DB. Don't have any issues with database connection, it connects.
But when trying to view a selected tables rows a small progress bar within a small dialog box titled "Display Results" appears saying "Waiting for Checking if Object is Editable" and the progress is stuck. Cannot see any data of the selected table.
I tried to export the schema and data, but it freezed at once. So I closed SQL Developer.
Tried to attempt that again but now cannot even view the tables details.
Used TOAD in another machine and connected using that, no issue then the table listed all the data. Checked on the remote machine using putty and "sqlplus" to connect and the data showed as expected.
So that tells me that something in my local machine is wrong. Cannot connect using SQL Developer. Has anyone out there faced similar issue? please any idea on this matter?
Thanks
Did you try connecting to any other database, remote and local ? Does this happen with every database or only one connection? Perhaps something is wrong with that installation folder of SQL Developer, perhaps something got corrupt while it was stuck. Perhaps try to download the latest version of SQL Developer from this link and try again.
I'm trying to connect my hosting providers SQL Server with LinqPad. It works fine using SSMS, but times out when trying to fetch the database list. I am successfully authenticated (via the test)... [ and if i change the credentials, it fails]...
Is there a way to extend the timeout??
Thanks - Kevin
The timeout for fetching schema information in LINQPad is 4 minutes, so something is going badly wrong if it times out! On the dialog, did you click 'Display all databases in TreeView' or did you connect to specific database?
One solution that our DBA mentioned is to set the database property "Auto Close" to false.
http://msdn.microsoft.com/en-us/library/ms188124.aspx
We did this on our development database server and it worked fine for linqpad with a few hundred databases.
Is there a way using sql 2008 Management Studio to look at the queries that hit the server? I'm trying to debug a program and I get messages like "Incorrect syntax near the keyword 'AND'". Since the queries are being dynamically generated it's a hassle to figure out what is going to the server.
Any help is appreciated!
There is a tool called Profiler that will tell you all information that you'll need. MSDN: http://msdn.microsoft.com/en-us/library/ms187929.aspx
I'm not aware of any method to do this using SQL Server Management Studio, but if you installed SSMS then you probably also installed the SQL Profiler. If you fire that up and run the TSQL_SPs profiler template, you can see every statement that's hitting the database.
Since the queries are being dynamically generated it's a hassle to figure out what is going to the server.
Why not just put the query that's generated into a message box, or print it to the console, or webpage, etc. ??
Trying to catch it at the DB server seems to be the long-way-around to debugging some simple ad-hoc queries.
Go to Management...Activity Monitor in the object explorer.
It's not live though, you will have to refresh it manually.
start up profiler from SSMS (Tools-->SQL Server Profiler), run a trace and select the T-SQL events
One option is to use SQL Server Profiler to run a trace. However, in some shops SQL Server permissions are set so only DBAs can run traces.
If you don't have sufficient rights to run a trace, then another option is to view the network traffic between the application that generates the SQL and box SQL Server is running on. WireShark works great for that.