I installed VS 2013. It installed SQL Server 2012 Express with LocalDB. That's great, except that I need full-text search, and it didn't install "Advanced Services" (and I didn't see an option during install).
I've downloaded SQL Server 2012 Express w/Advanced Services to add this, but it seems to want to install it on a new instance. Does this sound familiar to you? How did you add SQL Server Advanced Services to your LocalDB installation?
I had the same issue last VS version, and resorted to reinstalling SQL Server then. I apologize for coming to the community with a mundane question, but it vexes me. :)
Here's what I did:
start the SQL Server Express Advanced install
choose to modify an existing instance
check "full-text" under Instance Features / Database Engine Services
find that the installed instances list is empty at the "Instance Configuration" screen, and it wants to install a new instance
Looks like this cannot be done, unfortunately.
LocalDB is cool, but apparently not all-powerful.
Check out this existing post (among others):
Can't create an index catalog in localdb v\11.0
Check at Windows services, the Instance name (found within braces) for the SQL Server service.
Then,
start the SQL Server Express Advanced install
choose to modify an existing instance
check "full-text" under Instance Features / Database Engine Services
find that the installed instances list is empty at the "Instance Configuration" screen, and it wants to install a new instance...
At this point,
Manually type the instance name manually that you found at Windows services. (Instance name Case Sensitive though)
Related
I was installing TFS 2015 and was never given a chance to choose my database. I already had a SQL Server Enterprise installed and installation "wizard" proceeded to install SQL Server Express and then putting TFS database on it. I am not sure why it works this way, but is there any way to change this??
My TFS has nothing on it, I just installed it. I've read a lot of blogs about moving "Collection" from one DB to another, but I don't want to move the collection (it's empty and it's easy to do through admin console). I am trying to move the actual TFS' internal components from SQL Server Express to SQL Server on the same server.
UPDATE:
For anyone interested in knowing more about/how-to unconfigure TFS: Unconfigure Team Foundation Server
Copy the Tfs_Configuration database SQL Express instance to your full SQL Server instance, then run TFSConfig RemapDBs
An alternative, since you don't have any data: Just unconfigure your app tier and rerun the configuration wizard. Use the advanced configuration wizard and you'll have the opportunity to specify a database instance.
It's also worth noting that you should be installing TFS 2018, not TFS 2015, unless you have a very good reason. 2015 is 3 years old and two major releases behind.
I have a very fundamental and basic SQL question. Using Microsoft SQL Server Management Studio Express, how do I create my first Server? For that matter, how would I create it using any other required software tool?
I took a look at Sql Server Configuration Manager and I saw SQLEPRESS running as a SQL Server. But when I added that in to the start up widow for MSSM Studio Express, as the server name, it threw an error saying it cannot be found or does not exist. It seems that this is not the right kind of server.
To connect to the local instance of SQLEXPRESS, you will need localhost as the server name.
This is a fairly comprehensive guide on how to create a database once you have connected. All the steps won't apply to using SQL Express, but the gist of it is there.
In Object Explorer, connect to an instance of the SQL Server Database
Engine and then expand that instance.
Right-click Databases, and then
click New Database. In New Database, enter a database name.
To create
the database by accepting all default values, click OK; otherwise,
continue with the following optional steps.
Based on this comment:
Trying .\SQLEXPRESS in SQL Server Management Studio Express throws an error that says that "This version of Microsoft SQL Server Management Studio Express can only be used to connect to SQL Server 2005 servers". So this is the problem, I think.
.\SQLEXPRESS is the correct server name, but you have the wrong version of client tools (SQL Server Management Studio). To find out the version of SQL you are connecting to, there are a number of suggestions here: https://www.mssqltips.com/sqlservertip/1140/how-to-tell-what-sql-server-version-you-are-running/
But since you can't connect yet the easiest thing to do is go searching for sqlserver.exe, right click, properties, version. If you have multiple version you need take note of the folder that it's in and check the SQLExpress one. You can also check in services.
Once you've worked out the version, download and install just the management tools for that version.
This is my first time using it, I come from a PHP/MYSQL background and a client is asking me to assist with his MSSQL database and he gave me a file which is the exported database, it doesn't have an extension though.
I downloaded and installed Microsoft SQL Server Management studio but I'm not sure what to do, the tutorials online seem to be able to connect to the local server, on my end when I browse for a Server name I can't find anything under "Local server".
If it helps, the client have informed me that his previous developer (the one who seems to have had a conflict with the client and left) was using the same application with the server type set to "Database engine" and the Authentication set to "Windows Authentication", that's all the information I have.
Please help. Thanks.
If you installed a default instance of SQL Server with Management Studio, use the server name "localhost". If you only installed SQL Server Management Studio, you will need to at least download SQL Express: http://www.microsoft.com/en-us/server-cloud/products/sql-server-editions/sql-server-express.aspx
Also, note that if you develop in the latest version of SQL Server, you will not be able to back up and restore to the client's database if the client uses an older version. You will need to ensure all changes are scripted or use dacpacs (which you probably won't use).
I've installed Microsoft SQL Server 2008 Express twice now, and all the services work and I can create databases from Visual Studio 2010, but I don't have the Enterprise Manager (I learned it is now called Management Studio) available in the SQL Server 2008 program menu-- I do have other menu items like configuration manager, etc. but nothing for Management Studio / Enterprise Manager.
Is there a checkbox I've missed during installation?
I ran a search for all exes in the SQL Server root folder and nothing jumped out as belonging to the Enterprise Manager, but I'm not 100% sure what the executable would be named.
Primary question:
What is the procedure required to install the Management Studio client [for/with SQL 2008 Express] ?
Secondary question:
What is the name of this client's executable file ?
SQL Server Express doesn't come with SQL Server Management Studio (what you are really looking for when you say Enterprise Manager). You have to download it separately:
http://www.microsoft.com/download/en/details.aspx?id=7593
or with tools already as part of the download
http://www.microsoft.com/en-us/download/details.aspx?id=22973
It's kind of tricky installing Management Studio. This article walks you through it.
Here is an explanation of the situation:
The 2008 version of the Management Studio is not a stand alone installation and can only be installed as part of the SQL Server 2008 Express with Tools or Advanced installation.
Like many others, I spent countless hours trying to figure out how to
install the Management Studio for SQL Server 2008 Express - Advanced
installation (same should apply to the w/ Tools version). What
happened in my case was that I installed Visual Studio 2008 Express
and during that process a stripped down "Instance" of SQL Server 2008
was installed that did not include the Management Studio. Through
much pain and torture I learned that the Management Studio can only be
installed during installation of the first instance. To delete that
first instance, you must go to "Add or Remove Programs" and remove
"Microsoft SQL Server 2008". The removal process will only remove one
instance at a time and if you have installed more than one instance
you need to keep going until all instances have been removed and the
application completely disappears from the Add or Remove Programs"
dialog. Note: You do not need to uninstall any of the other SQL
Server 2008 applications that also appear in the "Add or Remove
Programs" dialog. Then go back through the install process as
follows: Double click on SQLEXPRADV_x86_ENU.exe to load the SQL Server
Installation Center and then go to Installation > New SQL Server
stand-alone installation. Then proceed through all of the
installation steps until you get to “Feature Selection” and click on
“Select All” to toggle on all of the Shared Features, which should
include Management Tools - Basic.Continue the process from there and
you should be good to go. Hopefully this will help others to avoid
much of the pain that many of us have already experienced.
The Management Studio exe is named ssms.exe.
The OP is not alone in his puzzlement about the "missing" management client!!! ;-)
The answers by DOK and CD Jorgensen found here were -collectively- among the most helpful I found while searching the web on this particular issue! At the risk of being redundant, I'm adding this answer with the goal of being more explicit and of safeguarding the key screenshots from Andrea Montanari's article referenced in DOK's answer.
Two things to know:
Not all installation packages for SQL Server 2008 Express Edition include the Management Studio.
You either need to ...
a) ... download the Install package for SQL Server 2008 Express with Tools (named something like SQLEXPRWT_cpu_language.exe: note the WT, short for With Tools) or an installer for an Edition of SQL Server other than Express.
or
b) ...download the Installer specific to Microsoft SQL Management Studio Express (same link as provided by CD Jorgensen). This installer only contains the Management Studio; it has none of the SQL Server per se.
[if you go with an a) install package]
The Management Studio (formerly Enterprise Manager) client remains a stand-alone, independent, component. However its installation is now triggered from a selection made as part of the "Install or Modify SQL Server" track.
It is not found in a separate "Install clients and Tools" menu item from the topmost dialog of the installer (as was the case with SQL 2005 and previous versions).
One should stress that it is stand-alone and the client can indeed be installed on hosts where the SQL Server [engine] is not, and will not be, installed at all. However the initial steps in the Installation Wizard give a strong impression that we will effectively install or re-install SQL Server. It is only on a subsequent step labelled Feature Selection that we have the ability to select Management Tools under Shared Features. On that same Feature Selection dialog we have the option of including or excluding, as desired, the installation of the SQL Server Engine and other Server supporting modules.
These are the two key dialogs of the wizard with regards to this issue:
The first one really appears to put you on track to install or mess with the SQL Server itself, the other dialog finally provides the opportunity of opting for the Client Tools (which include, mainly, the Management Studio). This same dialog also allows checking or un-checking the selection to install the Server per se.
Credits and more info:
The screenshots were taken from Andrea Montanari's article on the Insulin Power web site. This article referenced in DOK's answer provides a step-by-step description of the installation based on the "With Tools" installer.
As said in the introduction, I learned much from CD Jorgensen and DOK's answers; I'm merely making a few things more explicit, here, and correcting a few omissions (e.g. there are some installers which carry both the Server and the client, and it is not necessary to install the server).
I'm trying to do a SQL Server 2008 setup and I've been given a Cross Language Installation failure. More specifically:
Rule "cross language installation: failed.
the Setup language is different than the language of existing SQL Server features. To continue, use SQL Server Setup installation media of the same language as the installed SQL Server features.
I do not have SQL Server Express installed and I browsed through "Add or Remove Programs" and was unable to find anything that looked like it was a previous version of SQL.
Any tips?
I restarted the setup after facing the same problem, and I realized that man should not close the installation center till the setup process is completed. If you leave it open it will work.
Ensure that you have uninstalled all of your old SQL Server versions. Also you must restart the installer if you have not done that when you began installation.
All I had to do was exit the installer and start the process again. For some reason it worked the second time around.
I had the same problem today when installing SQL Server 2008 Express on a computer that has never had an instance of SQL Server installed.
I found that "Microsoft SQL Server 2005 Backward compatibility" was installed. I removed this via Add/Remove Programs and was able to successfully install SQL Server 2008 Express afterwards.
Change the Current Windows Language interface for the needed language you want to install.
That will make it possible for the Installer to launch the Localized version.
If you've previously installed SQL on the machine (or apparently some RedGate tools) have you checked for any SQL detritus in the registry?
If not then the MS forums have details of some reg keys to look out for, and some of the links are worth following for advice on what to delete from the registry.
On my installation of Sql Server 2008 Express, this was caused by having Sql Server 2005 Express Tools installed while trying to install 2008. Uninstalling 2005 Tools fixed the problem. I was able to keep Sql Server 2005 Express, including Sql Server 2005 Backward compatability; only had to nuke tools.