I've installed SQL Express 2008 on a 64-bit Windows 7 machine and have noticed that the Server Management Studio has duplicate toolbars, so that the standard toolbar shows, "File File Edit Edit" etc. The content of the toolbars is duplicated in a similar way. Has anyone else noticed similar issues?
This happened to me recently as well. When I went to add/remove buttons, and for each button, one was enabled and one was disabled.
Once I removed all of the enabled ones, the disabled ones were all that was left, and it went back to normal.
SSMS saves information about toolbar settings in .prf files.
Try to locate them in folder with path, similar to:
C:\Users\LOGINNAME\AppData\Roaming\Microsoft\Microsoft SQL Server\100\Tools\Shell
and delete .prf file with latest modification date. This will force SSMS to re-create all buttons/menues.
Related
I am attempting to compare schemas of two databases on the same server.
The two databases are named benchmarkdb and benchmarkdb_dev.
In Visual Studio 2017, I go to Tools > SQL Server > New Schema Compare...
From both drop down menus labeled "Select Source" and "Select Target" (as seen in the picture below), I want to select benchmarkdb as source and bencmarkdb_dev as target.
After clicking to select a source, the "Select Source Schema" pops up, and I clicked the "Select Connection..." button, which brought another popup. The newest popup (the one on the right in the picture below) shows both databases I am trying to compare.
However, after I choose one for either the source or the target, all pop ups close, but nothing populates the "Select Source..." or "Select Target..." drop down menus. In fact, it just goes back to looking like the first picture.
Is there a solution to this so I can compare the schemas between the databases?
Update:
I have tried this on VS 2012, 2015, and 2017. All are facing the same issue. VS software and system software are up to date. Below are some versions of software that I am using, if it is any help.
Windows 7 Enterprise SP1
VS 2012, 2015, and 2017
SQL Server 2014
.NET Framework v4.7.02053
OK, so I managed to fix it.
First off, you need to install SSDT from Microsoft pages. Just google it.
Make sure that you also have it listed in individual components when starting Installer (on Modify). Only SQL Server Database is required (I could choose from Integration Services and 3 more).
Next, you need to "Remove connection from history" in Schema Compare modal for connection selection.
I closed VS at this point, to make sure that the connection is not in history anymore.
Starting VS the next time, you should not have the problematic connection in history.
Recreate the connection (I checked "remember password") and voila. Schema compare works.
Not really sure, but in desperation I also installed "Redgate ReadyRoll Core", "Redgate SQL Prompt Core" and "Redgate SQL Search".
I don't think it matters, but if all else fails...
Edit: This worked on 2 machines and it doesn't seem to be connected to VS version.
I had the same issue, but I don't know if I had the same root cause.
My problems started after changing my database from SQL Server on a Window Server to SQL Server on a Linux Container. The schema compare would appear to accept my selection but the database field would never actually populate and I could not perform a comparison.
There were 2 things I had to do to solve the problem.
Update Visual Studio (using the standard updater within Visual Studio).
Update the SQL Server Development Tools (SSDT) add-on for Visual Studio to a preview version that supports SQL Server on Linux. That download is available here.
After both updates were in place I could select the database and execute Schema Comparisons between my project and SQL Server on Linux exactly as I had been doing for SQL Server on Windows.
If running a local database, check what version of SQL Management studio you are using
I had the same issue running Visual Studio Pro 2017 and SQL management studio v18.6 with SQL Server 2017 installed.
I tried all of the above solutions and no luck
Even going back to Visual Studio 2015 didn't work for me. What did work though was changing back to SQL Management Studio v17.9.1
No issues any more.
I may try to upgrade Visual Studio to 2017 again to see if that works now
i would like to ask if anybody having the similar problems like me.
i have downloaded the newest SQL Server Management Studio 2016 Preview from Microsoft web site, and after i installed it (successfully and i need to restart my notebook said the warning box) then, suddenly nothing happens, there is a folder on the start menu that says SQL Server Management Studio 2016, but the folder is self is empty and i do not see the app, first i thought must be i missed something, so i went back and repair those SSMS (through the Repair Menu), but still it is giving me the same error, does anybody here have the similar problem and a way out of it?, since i need this SSMS 2016 to query to my Azure SQL Database.
Thanks!.
Roland
That happened with me few times when i tried to install it in not the Administrator mode.
So, try to do that in elevated mode, if that will not help, try to download it again or just rollback to the older version (2014), as it works perfectly with the SQL Azure. SSMS 2016 is still in preview, so the unexpected behavior may happen.
So, it turns out that in Windows 10, all the start menu options may not show up. Try visiting C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft SQL Server 2016 RC3 in your File explorer to see if the SSMS shortcut is available there.
I'm sure this is very simple but I can't seem to find an answer to this at the moment and my googling powers have returned nothing.
I previously had an issue with an Addin and SSMS gave me the option to disable it (which I took). I have since reinstalled the plugin but it still does not appear as I previously disabled it.
Does anyone know where I can find the 'Add-In Manager' in SSMS 2008 R2 like in Visual studio?
For 2008 versions of SSMS you have to check this registry key:
Key="HKLM\Software\Microsoft\Microsoft SQL Server\100\Tools\Shell\AddIns\"
You will find there 1 entry per installed add-in. Every add-in entry has setting:
"LoadBehavior". Set it to "1" to make SSMS load add-in at start-up.
You can check and see if your add-in is located in either of these directories:
%PROGRAMDATA%\Application Data\Microsoft\MSEnvShared\Addins\
%APPDATA%\Microsoft\MSEnvShared\Addins\
I believe disabling an add-in will simply remove/move it from one or the other of those directories, or possibly change the extension.
SSMS doesn't have any official support from MS for add-in functionality, unfortunately, so is lacking in tools to manage the add-ins. They have also stated that they won't support your installation of SSMS if you have extensions installed for it. Read here for more: http://connect.microsoft.com/SQLServer/feedback/details/265567/ssms-allow-support-for-addins-as-in-visual-studio
I was in a middle of designing a website when suddenly Database Diagram folder just disappeared from the Database Explorer. I have no idea what happened and what to do right now, as I desperately need it to continue my work - adding tables to database manually are not an option for me.
I've been seeking for the solution for a whole day, and I even re-installed the Visual Studio and local IIS server, but it wasn't helpfull at all.
Is there any way to bring the feature back or at least is there any free tool that would work on Windows 8 x64 and has diagram-based database designer for MSSQL 2008?
EDIT
It seems that Microsoft removed the diagramming for purpose. Which is pretty logical in a business logic - why would somebody buy Server Management Studio if they have basic tool (diagramming) built in Visual Studio?
1) Database Diagram is a feature of SQL Server, not Visual Studio. I am not sure what VS uses to display that folder but you might want to verify with your DBA or check the configuration of the database to see if someone has not just disabled the ability to use diagrams. Have you tried refreshing your connection to the database server as well?
2) How is adding tables to a database manually not an option? If you get yourself dependent on doing things one way and only that one way you are setting yourself up for disaster in future projects, as you are in your current one. There are other ways from within VS to create a table, it just may not be a graphical picture that diagrams offers.
3) Have you looked at the database through SSMS to see if the diagrams folder shows up there?
Hello this has been my solution that worked for me and enabled me to use database diagram ide in visual studio 2012!!
First i installed SQL Server Management Studio. I then noticed that i still did not have SQLEXPRESS Service or SQL Agent Browser in my computer services either.. This was why i assume i couldn't login to any of the SSMS which was annoying. I then downloaded SQL Server Express R2 which then ran me though another setup which was fine. I did also choose to put a sql server password for SQL Server Express.
Once installed I double checked to make sure the services where running by right clicking MY COMPUTER / MANAGE / SERVICES -- scroll down till you see "SQL Server (SQLEXPRESS)" and make sure that the service has started and also "SQL Server Agent (SQLEXPRESS)" (this one was turned off when i checked) .. i was then able to login to SSMS without a problem.
I then created a new database, right clicked diagram like we always do in VS and created a diagram with two tables, created their relationships blah blah..
i then created a new website in vs 2012, i clicked "Connect To Database" in the SERVER EXPLORER"
I choose my server name, used windows authenication and selected the database i just created in SSMS.
Then to my suprise i now have database diagram designing in Visual Studio 2012.. Finally!
Thankyou microsoft for removing such a cool feature which now gives us developers a few things to do.
Hope this helps.
I don't suppose there's a way to emulate a FireFox-type of setup, whereby if I close SQL Server Management Studio (2008) my open tabs will be there again when I restart? I know I can save the individual windows into a .sql file but was wondering if there was a way for those tabs to reopen with the text in them on their own.
Any third party tools that do something like this, perhaps? Thanks for the advice.
-Larry
There is a built-in way to do mostly this, but it is not going to open any random tabs that were there when you closed SSMS.
You can create a Solution in SSMS and save it with any set of SQL scripts. This works much like Visual Studio. You can even save connections (server + login info). The FILE menu has options to "Close Solution" as well as "Open Project/Solution" and "Recent Projects and Solutions".
So, if you create a Solution, add some Queries (i.e. .sql scripts), and then close the solution either via the FILE menu or just closing SSMS, when you open that Solution again it will restore the tabs that you had open at the time the Solution / SSMS was closed.
I just tested this in SSMS 2012, though it might have started as far back as SQL Server 2005. Even if not in 2005, this feature should definitely be in 2008 / 2008 R2.
Not exactly as open-ended as the FireFox / Chrome feature as it requires a defined Solution with defined .sql files, but definitely close.
SSMS Tools pack (free up to SSMS 2008, for SSMS 2012 as paid upgrade)
Red Gate Tab Magic (no more standalone)
SQL Prompt
How about running the Studio inside a VMWare and simply suspend the VMWare between sessions?
For my development purposes I use a VMWare that only runs an instance of SQL Server and the Mangement Studio. Maybe it's overkill for DB development but it helps in testing the integration of the database into a networked environment.
Redgates SQLPrompt does exactly this. When you close you session (on purpose or if the session crashes), all previously open tabs will launch automatically when SSMS is reopened. If you choose not to automatically launch these tabs, they’re still available via the Tab History option.
The tool does cost money but the intellisense and Snippets feature that accompany it makes it value for money.