Goal: don't display the popup when you remove/delete the SQL document in SQL Server.
Problem: before I downloaded the latest version of SQL Server, it didn't show any popup about status when I removed the SQL document.
When I downloaded the latest version of SQL Server, it suddenly started to display the popup.
It always displays when I remove/delete the SQL document in SQL Server.
How do I remove it?
Thank you!
Uninstalling third-party SQL software permanently removed the "Querying transaction count" popup for me. Details are below.
I downloaded Devart's "SQL Tools" pack. It was one installation file
that installed the 15 separate applications into SQL Server Management Studio. I didn't even open any of the applications yet or activate the free trial (not sure if it activates automatically or not), and ever since have been receiving the "Querying transaction count" popup every time a query window is closed.
This was reducing my productivity, so I spent a few hours researching how to remove this popup so I don't have to click the close button thousands of times. SSMS didn't update, there weren't any options within SSMS or Devart to remove this popup, and there weren't any solutions online other than to create a macro to replicate multiple keyboard strokes to disconnect the connection first and then close the query window.
I ended up uninstalling these 15 applications, and without even needing to restart my PC, the "Querying transaction count" stopped appearing. As an added bonus, the annoying "Buy Devart" PC ads with the too-tiny-to-click-to-close-X that were also popping up every few hours (15+ popup ads a day during Black Friday sale too) stopped appearing as well! Hallelujah! Maybe someone else experiencing this "Querying transaction count" SELECT ##trancount popup installed third-party software like Devart's and just needs to uninstall it.
The software below looks amazing and I'm still interested in trying them out if the free trial didn't automatically activate and expire, but will probably install them one at a time so I can figure out which of the 15 programs is causing this popup. SQL Complete was the only one that I kept and is not causing the popup, so it's 1 of the other 14.
Devart's SQL Tools
SQL Complete (Not Causing Popup)
Source Control
Unit Test
Schema Compare
Data Compare
Data Generator
Documenter
Data Pump
Index Manager
Query Builder
Search
Monitor
Event Profiler
SQL Decryptor
DevOps Automation
Related
I'm pretty new to using QODBC for QuickBooks reporting. One of the first SELECT queries I prepared essentially flags customers with existing unused payments in the ReceivePayment table, querying against invoices with remaining balance for that same customer. The output is (or should be) a list of customers grouped by CustomerRefFullName, with a sum of unused payments in column #2, and sum of total balance remaining from open invoices.
It's a fairly simple query. When I import the table to MS Access as a static table, the query is fast as would be expected. However, when I run the query against a linked table, it takes upwards of 15 minutes to produce the results.
This should not be happening. Is this a MS Access misconfiguration issue? Something else relating to QODBC configuration that I am missing or unaware of? Any help would be appreciated.
I would like to inform you that when you Import QuickBooks data in the Access & run query, then obviously it will execute faster because all data available in a local MS Access table (offline). But when you execute query from linked table, QODBC is fetching data from QuickBooks. QODBC is an ODBC driver which uses QuickBooks SDK.
QODBC works by accepting SQL commands from applications through the ODBC interface, then converting those calls to navigational XML commands to the QuickBooks Accounting DBMS and returning record sets that qualify for the query results. This driver is not a Client/Server product, but rather communicates directly with the QuickBooks application as it runs. QuickBooks is a flat file database, and this driver will not change it into a relational database, so keep that in mind when developing with this driver.
QODBC acts as a 'wrapper' around the Intuit SDK so customers can finally get at their QuickBooks data using standard database tools; speeding development time.
Please keep in mind that QODBC is not a database tool, but rather a translation tool. Every transaction you request must be translated and communicated to QuickBooks via large complicated XML transactions.
The QuickBooks application layer needs to process those XML requests. The larger the number of Records, the lengthier the XML request, therefore QuickBooks may take more time and memory to process longer requests.
I would suggest you to enable QODBC status panel via QODBC Setup Screen->Message Window->Select "Display Driver Status" and "Display optimizer Status" options.
Then the next time you run a query, if you see “Waiting for QuickBooks”, it means QuickBooks is taking time to process the request. There will be a status panel at the lower right corner of your screen, will be shown a window with information on what QODBC is working at. Please note the step on which QODBC spends the most time or get stuck and share it with us.
I also suggest you to try executing below command on VB Demo and see it can resolve the issue:
SP_OPTIMIZEFULLSYNC ALL
This command will bring some data to a local cache to increase retrieval performance for queries. I would like to suggest you to please let run above command completely. Above command may take sometime depends on your records in QuickBooks. It may take 2-5 hours or more depends on the number of records in QuickBooks company file. Please let this command run completely do not kill this command. It is not advisable to kill/close the application while its building the Optimizer file.
Refer:
How to execute SP_OPTIMIZEUPDATESYNC or SP_OPTIMIZEFULLSYNC for Selected Tables
If you are still facing issues, I kindly request you to please raise a support ticket to the QODBC Technical Support department from below mentioned link & provide requested information:
http://support.qodbc.com
Also share more information about the issue you’re facing, so that we can locate the problem quickly.
We may need following information, Please attach below listed files when replying to the ticket.
1) Screenshot of QODBC Setup Screen -- > About (Start>>All Programs>> QODBC Driver for use with QuickBooks>> QODBC Setup Screen >> About Tab )
2) Screenshot of the issue you’re facing.
3) Share QuickBooks Version details: Press f2 on QuickBooks UI & share screenshot.
4) Share the SQL statement you’re using.
Share Entire Log Files as an attachment in text format from
5) QODBC Setup Screen -- > Messages -- > Review QODBC Messages
6) QODBC Setup Screen -- > Messages -- > Review SDK Messages
I am new to working with an AS400 green screen terminal and I am running some queries through the STRSQL command.
However, I cannot figure out how to clear the terminal screen to get rid of the past queries that were run.
An analogy; if im running command prompt and the screen gets too cluttered, i can run 'cls' to clear the screen. Is there a simular command on AS400?
You can press Shift-F1 (F13) and select option 3 "Remove all entries from current session". Then press Enter to confirm.
EDIT: Short answer: No. <- This is incorrect.
Long answer: you probably don't want to use STRSQL anyway. Use iNavigator (also on its way out) or IBM i Access for Web, which has a database interface. Another IBM offering is Data Studio. Alternatively, you could use any number of third party database tools like SQuirreL to do design work or for ad hoc queries. Basically, anything that uses ODBC / JDBC will work.
As a side note, the platform hasn't been called AS/400 for 20 years. Google searches for AS/400 are increasingly returning worse and worse results. A more modern name (only 10 years defunct) is iSeries. The current operating system is called IBM i, and the IBM web site is called the Knowledge Center. It's true that 'IBM i' doesn't yield the best search results, but that will never change unless we start using the term on the internet :-)
I use STRSQL all the time to prove an SQL statement either in my RPG or Web-based pgm.
I don't like clearing the historical statements because sometimes I find a hint, or a technique that I may need to reference again at some point.
With all that being said...
If your screen is "crowded" and you just want a brand new screen - simply page-down.
Oftentimes I need to troubleshoot a workbook that another person at my company has created and published to our server. To troubleshoot, I need to see their connection details, specifically their Custom SQL, to understand what data they are using in their extract.
Is there any way to view this connection info (specifically their SQL code) when viewing the published workbook on the server (web) version?
I am an admin and I am able to download their workbook to my desktop version of tableau, then open it, then reconnect to the data, then look through the data connections they created, to see their SQL. But it's a really cumbersome process.
All I'm looking to do is, when looking at a published workbook, see the data connection details so that I can see the Custom SQL, without going through the process of downloading I described above.
You can get some details on the SQL statement by creating a performance recording.
From the Tableau Server Admin Guide:
Enable Performance Recordings:
Choose the Admin button in Tableau Server.
Choose Site.
Select a site.
Choose Edit.
In the Edit Site dialog box, select Allow Performance Recording.
Choose OK.
You start performance recording for a specific view by adding ?:record_performance=yes to
the url. For example:
http://server.site.com/views/Variety/BaseballStatistics?:record_performance=yes
Now, notice a new link at the top of your view called "Show Performance Recording".
Click this to open the generated performance workbook dashboard. Click on the bar chart and observe the SQL appear at the bottom of the view. Note, the SQL text will truncate after about 250 characters.
The admin guide suggests viewing the "Tableau Log" to find the full SQL statement.. I have looked at all the server side logs in C:\ProgramData\Tableau\Tableau Server\data\tabsvc\logs but cannot locate the SQL. (please reply if you know where to find this?)
You can also run a database trace to see the SQL that the database sees. For example, for MS SQL Server, run the Profiler tool, setup a default trace, and filter on "Application Name" = "Tableau Protocol Server 8.0" or similar.
I have version 8.1 and this is how I got around this problem. Tableau shows a 'Custom SQL Warning' when you open a workbook that contains the custom SQL. You can copy all the text in this message by simply Ctrl + C as this is any other Windows warning message. And then paste it your editor of choice to analyze it.
I do not know if this works on earlier versions.
I thought you could do this easily, and originally answered that you could, but I didn't pay close attention to your question. You can change some things about data connections without editing the workbook, including the ip address or name of the database server, but there doesn't appear to be a simple way to access custom sql without downloading the workbook.
Go to the Administrator page and select Data Connections.
You can enter some search criteria to filter the list of data connections shown (or not).
Find the workbook in question by scanning the second column -- you can sort the column if that helps.
Then select the corresponding data connection in the 4th column to see the details of the connection.
If it makes sense for the connection, you can also modify the connection directly at the server. This is really useful if you, say, need to move your enterprise database to a new IP address or change a database password, without downloading, modifying and republishing alot of workbooks.
An even better practice is to start using shared data connections hosted on Tableau server instead of having each workbook have its own local copy of connection and related info.
I'm using Visual Studio 2012 for development. I really like using the SQL Server Object Explorer to work on database related tasks (queries, schema changes etc.). The issue is, every time I reload the IDE, I have to connect to the databases I work with. Is there a way to persist the list of databases like I can with the Server Explorer tab?
When you say you can't replicate, how long have you been using the explorer for to attempt to replicate it? It only loses the connections every now and then, so in fact right now I can't replicate it either, but over the next few days I'm sure they will get reset again!
It seems that there is something wrong with your VS IDE
It seems that this is a little bit unlikely as the same thing happened to me when I was running in VS 2012 beta running on Win 8 Release Preview too.
However I will try your suggestions and i'll see what happens, just to clarify are you saying that I run those commands once and then after that use VS as usual or are you saying that I try running in safe mode all the time?
Is reset settings same as the Import and Export settings->Reset All Settings menu item? (By the way I run with general development settings)
Anyone know where these connection settings are actually stored (registry, folder ...)?
Open VS. Don´t open any project or solution.
Add your databases in the Server Explorer.
Then File -> Save All
When I click on the "Databases" node in "Object Explorer" it just keeps on "Loading items" until at some point it just hangs.
This happens only when connecting to a remote server, not when accessing a database on my PC.
It also doesn't happen with any other node.
The guys at the web-hosting company didn't have any trouble with it. (But they're running 2008, and so is the SQL server there)
I reinstalled the whole SQL server etc. but to no avail.
What might be the problem?
I experienced this same problem: when accessing a remote server with the Object Explorer, SSMS would hang indefinitely. The Windows System Event Log would show DCOM error 10009 ("DCOM was unable to communicate with the computer MACHINE_NAME using any of the configured protocols.").
The solution was to clear the MRU history and other settings from my profile. To do that:
Close any open instances of SSMS 2012
In Explorer, open "%AppData%\Microsoft\SQL Server Management Studio"
Rename the "11.0" folder to something else, like "11.0.old"
Open SSMS 2012
You'll see that your MRU list has been cleared. You should then be able to re-enter your credentials and use SSMS as normal.
If everything works, you can delete the renamed folder. Otherwise, delete the new "11.0" folder that was created and rename the original one back to "11.0".
I have no idea whether it's actually the MRU list that's causing this problem or if it's some other profile data.
We were able to discover that SSMS is trying to make a DCOM connection over port 135 to the SQL Server (perhaps for SSIS, T-SQL Debugging, or something else). Our firewall was configured to block port 135. By opening the port in the firewall we were able to use SSMS (hence the reason it worked against local databases but not remote ones). Unfortunately, an open port 135 is an invitation for a lot of attacks, so that wasn't a practical solution for us.
Turn Auto-Close off on all the databases. Worked like a charm to me!
Every time you expand or refresh the database list, server has to awake the databases causing the hang.
Just run this to find all the databases that have auto-close on
SELECT name, is_auto_close_on
FROM master.sys.databases AS dtb
WHERE is_auto_close_on = 1
ORDER BY name
Credits to http://social.msdn.microsoft.com/Forums/sqlserver/en-US/99bbcb47-d4b5-4ec0-9e91-b1a23a655844/ssms-2012-extremely-slow-expanding-databases?forum=sqltools
To turn-off this setting for a database - Right click on database instance in object explorer -> Click properties -> Click "Options" in left navigation pane in database properties window -> Change the value of Auto Close property to "False" in right pane as shown in the snapshot below:
Assuming you have access to only one database at the hosting company (which is almost always the case, at least with a certain username/password), you can avoid the need to use the dropdown at all by setting your registered server to default to the database you're supposed to access:
(It may take longer here, too, but this will be one-time. You can also type it instead of waiting for the list to populate.)
This way, even if the login the host created for you routes you to tempdb or something by default, Management Studio will still put you in the context of your database.
I see now that you are talking about the Object Explorer node, not the "Use database" dropdown that I somehow interpreted incorrectly. An exercise to try might be to highlight the databases node (don't expand it) and click on F7 (Object Explorer Details). If this loads for you then it can be an alternative to navigate through the hierarchy and, as a bonus, you can show lots of entity attributes here and also multi-select, two things you have no control over in Object Explorer.
If that doesn't help, then your host should be helping you better than they appear to be. If SSMS 2012 is supported then they should be able to test this in SSMS 2012 and confirm or deny that they can reproduce it. If it is not supported then I think your recourse is to install SSMS 2008 as well (they can co-exist) and use it for managing this specific server.
Of course, just about anything that you can do in Object Explorer (and plenty of things you can't), you can do by using the catalog views and/or DMVs. So before you determine what to do, you may want to review (or share with us) exactly what you are using Object Explorer for - if there is a way to do it without Object Explorer, you might like the workaround better than having two versions of the tool (since the improvements in 2012 SSMS have absolutely nothing to do with Object Explorer).
In my case deleting the profile folder worked exactly once. The next time I opened SSMS 2012 it would freeze again when connecting to a server. SP1 didn't fix this either.
That was until I found the following simple workaround described on a ticket by Ben Amada over at connect.microsoft.com: Always close the Object Explorer Details before closing SSMS 2012.
So the complete workaround for me is this:
Follow Jaecen's answer, but close SSMS 2012 again after it created a clean profile folder
Apply Hoodlum's recommendation and copy SqlStudio.bin from the old profile folder to the new one (the old profile folder can be deleted afterwards)
Everytime before closing SSMS 2012 make sure the Object Explorer Details window is closed
The first two steps are required only once, or if the Object Explorer Details window was left open accidentally.
Edit
I just noticed that closing the Object Explorer Details window is also required when (re-)connecting to an SQL server in the same SSMS session. So basically whenever connecting to a server the Object Explorer Details windows has to be closed.
I spent over a month with Microsoft SQL Support troubleshooting this. It has been submitted as a bug.
I have both SQL 2012 SSMS and VS 2012 installed on Win 7 (64).
Deleting the profile folder never worked for any reasonable length of time.
The workaround we found was to ensure that my SSMS profile defaulted to the Master database when connecting. It appeared to have something to do with the fact that I'm connecting with Windows Authentication and I belong to more than one AD group that have SQL permissions assigned AND I don't have SQL specific permissions set up on my AD account.
I am connecting to several remote servers rangig from 2000 to 2012.
SMSS on local PC is SQL Server 2012,SMSS is 11.0.2100.60
SSMS freezes several times a day.When this occurs, I go via RDP to the
local server / SMSS / Activity Monitor and kill the processes from my PC with Database Name = master, one at a time, until SMSS on my PC unfreezes.
This always works, however, a cure for the disease raher than the symptoms would be highly welcome.
Have some SQL Servers from 2000 to 2012,
access then through SMSS from my desktop.
Problem occurs with varying frequency, looks like this: when I collapse a server in object explorer, SMSS freezes.
looking in activity monitor on the server in question, i find a process in master db with host = my desktop executing the following query
SELECT dtb.name AS [Name] FROM master.dbo.sysdatabases AS dtb ORDER BY [Name] ASC SMSS
killing the process frees SMSS.
Here is what worked for me
Open SSMS
click on connect to object explorer button
in the connect to server dialog box expand options >>
click reset all
Done!
I've test approximately all above answers but my SSMS got stuck in expanding the database list. I found the problem finally. The problem was because of a database that I restored it but It did restore correctly at the end. Then When I expanded the database list it was sticking.
I run a the query
SELECT
dtb.name AS [Name]
,dtb.database_id AS [ID]
,CAST(has_dbaccess(dtb.name) AS bit) AS [IsAccessible] FROM master.sys.databases AS dtb
Then the result took too long and at the end timed out but When I filter the stuck database I got result.
SELECT
dtb.name AS [Name]
,dtb.database_id AS [ID]
,CAST(has_dbaccess(dtb.name) AS bit) AS [IsAccessible] FROM
master.sys.databases AS dtb
Where name <> 'StuckDB' ORDER BY [Name] ASC
At the end I decided to detach StuckDB to solve my problem.
I have now applied SQL 2012 Service Pack 1 (through Windows Update) and it seems to work fine now, though it does take a very long time to load.
"Open SSMS click on connect to object explorer button in the connect to server dialog box expand options >> click reset all" - it works
I solved this problem by changing my default database back to master.
Go to database properties at SSMS and change compatibility to 2012. Then check.