Is it possible to run SQL Server Management Studio Express from CD without installing it on the computer?
I need it sometimes to provide support for the client but do not want to install/uninstall it.
If you're doing basic support, you can simply use SQLCMD to run queries/procs. Other than that I don't think there is any way to run it without installing it. There are a few questions on SO about alternatives to Management Studio that you may be able to install on a cd/key though.
No, you can't you have to install it
can you not connect remotely maybe?
You have to install it as far as I know.
The SQL 2000 isqlw.exe is standalone, IIRC, and can manage SQL 2005 to a point.
Related
I was thinking of the minimum software I can install on my new dev machine. Has anyone tried codeing with just VS2010/Linqpad?
The SQL Server is on another machine so then I would only need SSMS.. but then I think linqpad could replace that + help me with Linq queries..
But the problem seems to be I won't be able to CREATE SQL USERS with SSMS and I may need to do thatfrom time to time..
Any thoughts ?
Personally I'd always install SQL Management Studio as it's the defacto tool for managing SQL Server.
AFAIK you can't issue arbitary SQL commands using VS2010 and thus you can't create users - that is unless you use VS2010 to write an app to issue the commands which is trivial but I'd say ultimately pointless.
LINQPad lets you run SQL queries as well as LINQ queries - so you can manage without SSMS if you're happy to do things purely via SQL.
Of course, for some things SSMS is easier than writing SQL. And on a dev box you'll probably want SQL Profiler, too (for this reason, it's a good idea to install the management tools that come with the full edition of SQL Server rather than relying on the SQL Express tools).
I would install SQL Server client tools - you would at least then get SSMS and SQLCMD. No need for SQL Server itself (or even SSIS - you can still use BIDS to write packages, but you have to run them interactively).
I want to install sqlserver2005 on my server2003 machine. I heard that sqlserver2005 should be installed prior to visualstudio2005. Is it right or wrong?
can we install sqlserver2005 before installing vs2005? - Yes
i heard that sqlserver2005 should be installed prior to visualstudio2005. is it right or wrong? - not necessarily, but it depends on what parts of SQL you are using.
This link should give you the answer
In short
The issue is that if you install
Visual Studio first, SQL Server
Express will be installed if there is
not a local instance of SQL already
installed. When you later attempt to
install the SQL Server 2005
workstation tools it will fail, but
you are not blatantly alerted to that
fact.
They are independent of each other. It shouldn't make a difference which one you install first.
Or will everything explode and kill a couple of kittens?
Absolutely. The engines are isolated from each other, so, you can run both in parallel or remove/uninstall components if you need.
Hope this helps!
That should be safe.
What we have had problems with is: if we install SQL Express first, then the management console will not install, when you install SQL Server.
I had kitten parts splattered everywhere when I tried to do exactly what you are asking about. So I burned it all down and reinstalled, installing SQL Server 2008 first, and then making sure to de-select the database components in the Visual Studio installations.
So far so good, but my SQL Server installation is used sparingly.
I need to build SSIS packages on a build machine, and do not want the overhead of installing SQL Server Management Studio on this machine. A SQL Server 2008 SDK would be ideal, but I could not find where to download it.
The dlls I require are (for example):
Microsoft.SQLServer.ManagedDTS
Microsoft.SqlServer.PipelineHost
Microsoft.SqlServer.DTSPipelineWrap
Microsoft.SQLServer.DTSRuntimeWrap
I could attempt to copy them to the build machine individually, but I would rather just use an SDK if possible.
Where can I get the SDK, or alternatively, what suggestions are there?
You could probably manually copy things about and register then in the GAC, but the client tools are hardly huge, and don't take long to install, so I don't see why they are much of an overhead?
As far as I know there's no other way to get those assemblies.
I think he is trying to accomplish SSIS packages as part of the automated continuous build process. The way i did it was to have an express edition of SQL Server and SSIS on the build machine, use BIDS helper to script the cmd line file for deploying the packages and use NANT to use this script. Hope this helped.
I don't know about SQL 2008 but SQL 2005 SSIS packages are developed in Visual Studio.
Edited:
When you run install for client tools, it's an option to add the stuff to VS.NET, "Client tools" as such can be deselected (end edit)
SSMS can be used to manage them and administer.
What other editor did you want to use...?
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.