I just downloaded SQL Server 2005 Express edition. I was hoping it would come with a GUI to let me design my tables and such, but it doesn't. I'm working with ColdFusion/CF Builder here, so I don't really want one that integrates into Visual Studio. Also, it would be helpful if it has the option to connect to a remote database too. Suggestions?
SQL Server Management Studio Express should have been installed with your download. If not, you can get it here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en
Consider using the latest version of SQL Server Express (2008), which can be found here:
http://www.microsoft.com/express/Database/
The path for SSMS in the 2008 edition is
"C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe"
I would imagine that on 2005 the path will be the same but replace the 100 with 90. If it is not there then you can redownload it and add it to your instalation
Related
Getting an error in SQL Server 2000 Enterprise manager - Please see in the attached screenshot!
Kindly help how to overcome the issue
You have to install the backward compatibility package. You can download it from here.The file is called SQLServer2005_BCxxx.msi
You're trying to access a SQL Server 2005 instance using SQL Server 2000's Enterprise Manager, which isn't possible.
You need to install a copy of SQL Server Management Studio - the 2008 R2Express version should be fine, or you can dig out the 2005 version
Do visual studio 2010 include already Sql Server instance, or I need to install Sql Server developer edition to develop an application that need a Sql Server db.
If it installs a Sql Server express edition, it this enough or it's better to have Sql Server developer edition?
I would second that installing the "full" SQL Server Development Edition makes sense if you do serious database development.
However you can have both installed side by side, and having SQL Server Express is very useful for one reason - it supports placing database files in the App_Data folder of ASP.NET applications. While I don't do this for my own projects, it's a very nice feature for demos or open source applications you download from the web: just unzip, start VS, hit F5, and you have a running solution including database. Without SQL Express, you first have to move the MDF file, attach the database, set up user rights, replace the connection strings etc...
The Visual Studio 2010 installer gives you the option of installing SQL Server 2008 Express Edition. This edition of SQL Server is good enough for development purposes but is not intended for production use.
I think the size limitation is not the main issue.
In Sql Server 2008 you have some features in Sql Server Management Studio that aren't available in the Express management Studio or the Express database engine, like:
- suggesting the table and column names (in Query Window)
- Sql profiler
Cor Westra
my colleague created .mdf and .ldf files from Visual Studio. Now, I'm trying to access the file in SQL Server. There seems to be a problem with this. Can anybody tell me what edition of SQL Server must I have on my Windows Vista 32-bit, so I can access this database. Thanks in advance. :)
Your question is tagged [visual-studio-2008]. That version of Visual Studio is bundled with SQL Server 2005 (if you have the proper edition) and the builtin tools uses SQL Server 2005. However, there is nothing in Visual Studio 2008 that prohibits you from using say SQL Server 2008 if you want to. But I hope this answers your question.
The MDF and LDF file format is identical between all SQL Server editions that are at the same build number. Your friend's Visual Studio by default installs SQL Server Express 2008, and the Express is updated automatically by Microsoft Update and Windows Update to the lates released service pack. Since there is no supported downgrade path for MDF files, your own SQL Server has to match at least the latest Express edition pushed through Windows Update, so you'll most likely need SQL Server 2008 SP1 (build 2007.100.2531.0).
To verify what version of SQL you have and your friend has, follow the steps described in How to identify your SQL Server version and edition
When I try to install a new instance of SQL Server 2008 Express on a development machine with SQL 2005 Express already up and running, the install validation fails because the "SQL 2005 Express tools" are installed and I'm told to remove them.
What exactly does that mean?
After reading this article:
http://www.asql.biz/Articoli/SQLX08/Art1_5.aspx
I uninstalled the 2005 version of the SQL Management Studio but received the same error from the 2008 installer during my follow-up attempt.
Updates
1) Uninstalled the SQL 2005 Management Studio only. Received the same error from the 2008 install.
2) Removed all SQL 2005 common components. Received the same error from the 2008 install.
3) Installed the shared components from the SQL 2008 installation program. Received the same error from the 2008 install when trying to install the new SQL 2008 instance.
4) Uninstalled SQL 2008 components, rebooted, re-installed SQL 2005 Management Studio from installation media, rebooted, un-installed SQL 2005 Workstation Components from Control Panel, re-booted.
Installation of SQL 2008 is now proceeding as it should.
Seems likely that if I'd re-booted after update 2 above things would have gone more smoothly. :-(
Although you should have no problem running a 2005 instance of the database engine beside a 2008 instance, The tools are installed into a shared directory, so you can't have two versions of the tools installed. Fortunately, the 2008 tools are backwards-compatible. As we speak, I'm using SSMS 2008 and Profiler 2008 to manage my 2005 Express instances. Works great.
Before installing the 2008 tools, you need to remove any and all "shared" components from 2005. Try going to your Add/Remove programs control panel, find Microsoft SQL Server 2005, and click "Change." Then choose "Workstation Components" and remove everything there (this will not remove your database engine).
I believe the 2008 installer also has an option to upgrade shared components only. You might try that. Good luck!
In my case even after uninstalling all 2005 related components it didn't worked. I had to resort to a brute force way and remove following registry keys
32 Bit OS: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90
64 Bit OS: HKLM\Software\Wow6432Node\Microsoft\Microsoft SQL Server\90
I had to unistall the Workstation Components and SSMS Tools Pack (SSMS Tools Pack is an add-in for Microsoft SQL Server Management Studio (SSMS) including SSMS Express.)
Installation of SQL 2008 is now proceeding as it should.
The problem is that SQL 2008 MS has a bug where connecting to a remote server (say like a service provider collocation) it will always try to open the fist db in the list, and since the possibilities of been ur db the first on the list are really low, it will throw and error and fail to display the list of dbs... which using sql 2005 management studio it just works.
Wished I could use SQL 2008 MS, but looks like as far I connect to remote SQL 2005, SQL 2008 is out of the question on my dev machine :(
Just Remove the the Workstation Components from Add/Remove Programs - SQL Server 2005.
Removing Workstation Components, SQL Server 2008 installation goes well.
Simply remove the Microsoft SQL Server Management Studio Express 2005 from control panel
N.B. These notes are for SQL Server Express 2008 R2 (so Microsoft still haven't made this any easier). I also realise that I complicated things by installing 32-bit SQL Server Express 2005 and 64-bit SQL Server Express 2008.
I followed the steps by Josh Hinman above. Uninstalling the SQL Server Express 2005 "Workstation Components" was not enough. I required an uninstall of the 2005 Management Studio as well.
I also tried the Upgrade route that Josh Hinman suggested by clicking on the 'Upgrade from SQL Server 2000, SQL Server 2005 or SQL Server 2008'. This route never gave me the option of installing the components side-by-side it just went straight through the process of upgrading from 2005 to 2008. It completed successfully - but hadn't actually done anything. Thankfully though it hadn't harmed any existing database instances. So be warned trying that route.
If you currently have Red Gate SQL Toolbelt, you will need to unistall that too before continuing. Somehow it adds a reference to the 2005 version of the SQL Management Studio.
I'am trying to install SQL SERVER developer 2008 R2 alongside SQL SERVER 2005 EXPRESS,
i went to program features, clicked on unistall SQL SERVER 2005 EXPRESS, and only checked, WORKSTATION COMPONENTS, it unistalled: support files, sql mngmt studio
After that installation of sql 2008 r2 developer went ok....
Hopes this helps somebody
I also had to remove the SMSS before it would get past that step.
I'm trying some of the ASP.NET MVC tutorials and one of them has the following steps:
Right-click on the "App_Data" folder, and choose "Add New item"
Choose "SQL Server Database" under the "Data" category.
However, once I do that, I get the following message from Visual Studio:
Connections to SQL Server files (*.mdf) require SQL Server Express 2005 to function proprely. Please verify the installation of the component or download from the URL...
The thing is that I have SQL Server 2008 Developer Edition installed, and I would really rather not install any Express versions (2005 or 2008) if I don't have to. Is there a work-around for this issue?
I ran into this problem too on 64-bit Windows 7 (using 64-bit SQL Server Express 2008).
There are two methods of fixing this problem referenced in the Microsoft Support Knowledge Base article:
1. Workaround
To work around this problem, uninstall
the 64-bit version of SQL Server
Express 2008, and then install the
32-bit version of SQL Server Express
2008.
If you don't want to do the uninstall/install, then try the Hotfix method below.
2. Hotfix
A supported hotfix is now available
from Microsoft. However, it is
intended to correct only the problem
that this article describes. Apply it
only to systems that are experiencing
this specific problem.
Although the article itself doesn't include a link to the hotfix, you can get it here:
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=957944
To illuminate masfenix's reply, SQL Express supports one feature that is not supported by full-blown SQL Server: a "user instance" database. With SQL Express installed and an mdf file in your App_Data folder, the application will dynamically attach and detach it as needed. For hobbyist or small business sites, this may be perfect. If you're running SQL elsewhere in the enterprise, you probably don't want to go this route and therefore the feature isn't useful to you.
Actually SQL express is a whole different database engine then SQL Server 2005. So yes if you want to use mdf files you'd need SQL Express.
I want to point out that I have both Developer edition and Express edition installed. And I still run into the same error. I think Express edition must be installed as a single instance.
I have the same problem but I've sql 2008 express installed.
any way to make it work with sql 2008 express so I don't have to install the 4th sql instance on my machine??
I already have sql 2005, sql 2008, sql 2008 express
what the F... :)