I have nearly 15 SQL Instances names in the Database combobox of SQL Management Studio, now i am using only one and want to remove all the others from that combobox..
They should either be stored in Windows Registry
Thanks for the help...
Have you uninstalled the instances?
If they are still in the drop down after that , just search for them in the registry...
Related
My development environment
Windows 10 2004 64 bit
Visual Studio 2019 Community Edition Version 16.7.6
SQL Server 2019
EzAPI2016
Working with EzAPI to implement a sample workflow that read a table and write to another temp table in the same database. After create the OLEDB data source providing the corresponding data-flow context, when assign the connection-manager to the connection attribute of the previously crated source object, the error in the title happen.
Thanks in advance for any suggestion.
Have a good day.
Solved:
Found the solution removing the reference to Microsoft.SqlSever.DTSRuntimeWrap.dll (version 13) into the ezapi project, and updating it to version 15, in my environment under c:\windows\Microsoft.net folder.
Over the weekend my corporate PC got patched (without warning!) and my instance of SQL Server 2008 R2 was removed leaving behind it's MSSQL\DATA folder containing the .mdf and .ldf files.
I am now installing SQL Server 2014 (we still run Win 7 so cannot go to 2016).
Is it possible to import and upgrade all the old databases into SQL Server 2014?
I am aware that I can attach the existing files but that leaves them in the old MSSQL10_50.MSSQLSERVER folder.
Is it simply a case of moving the files to the MSSQL12.MSSQLSERVER folder, attaching, and then changing the Compatibility Level?
Yes, you should be able to just simply attach the existing .mdf files and update the compatibility level and be done with it :-)
Going from an older version of SQL Server (2008 R2 in your case) to a newer one (2014) should never really be a problem (unless you wait too long to upgrade - you cannot go from 2000 to 2014 directly anymore).
The other way around never works - you can never go from a newer version (e.g. your 2014) back to an older one - there's just simply no way to do this (other than scripting our your database structure and contents into SQL files and running those against the other instance)
I am trying to debug a program using Entity Framework code first on my personal (work) computer.
We have recently had a domain migration, meaning that the user I log in as now is not the same that I used before. This caused me to loose access to the databases I had on the computer. To get around this, I have uninstalled everything to do with Microsoft SQL Server on the computer, and installed the latest version of Microsoft SQL Server, 2014 - 12.0.4213.0 . I then restored the database I need.
When I first tried to run the program, Visual Studio complained that the project is set up to use SQL Server Express, which was not installed. The recommended solution is to change the project to use SQL Server instead. To do this, I must click on "the database file" and follow the instructions. I have looked through the entire solution. There is a great many files, but I found no good candidate for "the database file."
It seems that my Google fu is not strong enough to find anything about this. So my question is: how do I change the project to use SQL Server?
I also have a second, related question. I tried to solve the problem by installing SQL Server Express. However, when I try to restore the database to this, no base appears in the drop down list. When I try to run the program now, I get another error:
Unable to create the file 'c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\Timelønsblanket.mdf' because it already exists.
I guess that this is also why I cannot restore the database. What I have found in websearches warns that I should not manually delete .mdf files.
Any advice on what to do?
I have solved the problem. All that was needed was a correct connection string. No need to find a "database file".
I use Visual Studio 2013 Professional Update 4 in combination with multiple SQL Server 2012 Enterprise servers/instances. The Idea was to create a Version controlled deployment using a Visual Studio Solution with SQL Server Projects.
However for some reason the "Update Target" and "Generate Script" button is disabled.
I can update the local database project from the sql server database but the other way around is not working. (see screenshot)
Google is not helpful at all although I found a few people with a similar problem.
Update target button is disabled after schema comparison
VS2012: Schema compare, update button disabled
VS2012 Schema compare buttons disabled
But none of this questions/blogposts is about Visual Studio 2013 and in addition none of the proposed solutions is working for me.
Question: Why is the Update Target button disabled and what do I have to change to fix this?
Note: Of course, I'm using the latest version of SQL Server Data Tools(12.0.50318.0)
This was driving me nuts, as well. I finally noticed a "warning" message stating "Cannot generate deployment plan due to an internal error". Because of this, the Update and Generate Script buttons were both disabled.
I resolved this by closing Visual Studio, navigating to the folder containing the Database project and removing all (*.dbmdl) files. I then restarted Visual Studio, re-ran the compare schema and the Update button was enabled.
The tip that helped me was to look at the error list. (View Menu, Error List). Once I cleared the errors (just the errors, the ones with the red X) I was able to compare the schema again and the Update and Generate Scripts buttons were both enabled.
Beside the generate script, click on OPTIONS and select only the objects for which you want to compare.
This and ONLY this worked for me.
I have some issue I can't find any info about!
I did a clean install, and VS2010 was not yet installed when it occured!
My colleagues don't seem to have this issue while having exactly the same software!
Sql Server 2008 R2 is fully up to date with SP1 etc.
The issue:
My intellisense works!
For example when I type SELECT * FROM --> right after the last space I see my schema or database or table names!
What doesn't work is:
When I continue SELECT * FROM ma" --> now the database "master" is selected! Normally when I type "." (a dot) I would get SELECT * FROM master., but I just get SELECT * FROM ma.
This is SOOO annoying!!
I have fixed this in the past by installing a Management Studio from the NON R2 version, but I just have a fresh install and I would like to know how to fix this, or at least know the cause?
I hope I described my issue properly!
Kind regards,
Wim
This behavior was changed at some point. I have to type Enter and then the dot in SQL Server 2008 R2.
In SQL Server 2012, when you see the auto-complete list, you need another keystroke to actually select it (e.g. down-arrow), then the dot works. You may want to download SQL Server 2012 RC0 and see if the updated IntelliSense functionality is slightly better (though, admittedly, not perfect and still not how it used to work).
In case you're worried that SSMS 2012 is not worth your time yet, please see this question over on ASK SSC: http://ask.sqlservercentral.com/questions/86305/sql-server-2012-ready-to-use.html