Comments
Sort by recent activity
You are correct. SQL Prompt appears to be fine and SQL DOC is installed, but is not available from SSMS. I am using SSMS 2008.
Microsoft SQL Server Management Studio 10.0.5520.0
Microsoft Analysis Services Client Tools 10.0.5500.0
Microsoft Data Access Components (MDAC) 6.1.7601.17514
Microsoft MSXML 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 9.0.8112.16421
Microsoft .NET Framework 2.0.50727.5483
Operating System 6.1.7601 / comments
You are correct. SQL Prompt appears to be fine and SQL DOC is installed, but is not available from SSMS. I am using SSMS 2008.
Microsoft SQL Server Management Studio 10.0.5520.0
Microsoft An...
As the other user did, I uninstalled SQL Test and SQL Search, then installed them. All is well with the world. Lost some time, but I am glad that things are working again.
Larry / comments
As the other user did, I uninstalled SQL Test and SQL Search, then installed them. All is well with the world. Lost some time, but I am glad that things are working again.
Larry
I hope this fixes my problem as well. I "upgrade" to the new SQL Toolkit set of products yesterday and now none of my add-in in SSMS work. Even SQL Prompt is hokey. I will attempt to uninstall SQL Doc from my machine and reboot and see if this fixes my issues. Email on results to come momentarily. / comments
I hope this fixes my problem as well. I "upgrade" to the new SQL Toolkit set of products yesterday and now none of my add-in in SSMS work. Even SQL Prompt is hokey. I will attempt to uninstall S...
Uninstalling SQL Doc 3 did not fix the issue. I also rebooted just to be sure, but the same result. Reinstalling SQL Doc 3 from the SQL Toolbelt executable did not fix the issue.
I am on SQL Prompt 6.3.0.354. The buttons for Add-ins, SQL Search and SQL Test are greyed out (unavailable). The buttons for SQL Source Control and Tab History are available for use.
Is there a workaround since the above process did not fix the issue for me.
Regards,
Larry / comments
Uninstalling SQL Doc 3 did not fix the issue. I also rebooted just to be sure, but the same result. Reinstalling SQL Doc 3 from the SQL Toolbelt executable did not fix the issue.
I am on SQL Prompt...
Here are some free times for this week;
Today from 3:00 - 4:00 PM EDT
Tomorrow most of the day.
Thurs. 1:00-4:00 PM EDT
Friday 9:00-11:30 AM EDT / comments
Here are some free times for this week;
Today from 3:00 - 4:00 PM EDT
Tomorrow most of the day.
Thurs. 1:00-4:00 PM EDT
Friday 9:00-11:30 AM EDT
That's fine. And for upfrontness, I just checked. I am on version 6.3.0.345 and I am running SQL Search 2.0.1.8 / comments
That's fine. And for upfrontness, I just checked. I am on version 6.3.0.345 and I am running SQL Search 2.0.1.8
Email address is lmeklemburg@intellicorp.net / comments
Email address is lmeklemburg@intellicorp.net
David,
I am the DBA for the organization. I am the sysadm on all our database servers. I will look at the permissions at a more granular level, but as a beta tester for your product, I knew most of what you stated. I would not have posted this if I thought something else wasn't going on.
Larry / comments
David,
I am the DBA for the organization. I am the sysadm on all our database servers. I will look at the permissions at a more granular level, but as a beta tester for your product, I knew most of...
That is correct. It happened to me again this morning. In SSMS, on the status line it shows the correct server and database, but SQLPrompt tells me that the identical database is not found in sysdatabases and then the entire sets of objects in the select statement are marked, but the query runs fine.
Sorry for the slow response, / comments
That is correct. It happened to me again this morning. In SSMS, on the status line it shows the correct server and database, but SQLPrompt tells me that the identical database is not found in sys...
Any progress on this ticket? / comments
Any progress on this ticket?