Updating version of SQL Server 2008 Management Studio - sql

I am currently running SQL Server 2008 Management Studio (version 10.0.1600.22) and I want to update due to a bug in this version.
All the documentation I have found so far has been for updating to SQL Server 2008 R2 Management Studio and SQL Server 2008 Management Studio Express which I believe are different. Is that right?
I have also found links for updating SQL Server which I once again believe isn't what I'm looking for as I only want to update the client side.
Is there a way (or link) where I can update SQL Server 2008 Management Studio without having to reinstall it?

I believe the management tools for SQL Server 2008 R2 is backwards compatible with SQL Server 2008.
If you want to keep your database instance SQL Server 2008, just run the setup on the installation DVD and choose Maintenance -> Repair. At the screen to select the instance, there is an option to select "Repair shared features only". I don't have SQL Server 2008 DVD, only 2008 R2 DVD, but I believe the 2008 version works the same way.
Or if your computer doesn't have SQL Server database instance, you can do a fresh installation and choose only management tools. Example screen shots (for 2008 R2): http://it-n-careerz.blogspot.com/2013/04/how-to-install-sql-server-management.html
Good luck!

Related

Developing on SSMS 2016 for SQL Server 2008 R2 database

I'm developing for a database that's running on SQL Server 2008 R2. Is there any reason I can't develop on SSMS 2016 and deploy those scripts onto production? Or do I have to use SSMS 2008 R2 for development as well?
SSMS is typically backward compatible.
If you are working in a query editor window, the yellow ribbon at the bottom displays your connection status and the SQL Server version number you are connected to. SQL Server 2008 R2 will be version 10.5. When you run the sql script, the features available are based on that version of sql server you are connected to. This is regardless of plugins and add-ons.

SQL server version 655

what update i need to install for version 655 in vs studio 2010 for the sql server.
Can anyone tell me what i need on my computer when creating a database using sql on vs studio 2010? I need to use version 655 cos thats the version being used on Uni Computers
SQL Server 2008 (655) and SQL Server 2008 R2 (661) are not the same thing (though it is a common misconception - a lot of people think they're the same because Microsoft made a terrible, terrible, terrible naming decision, making 2008 R2 sound like a service pack).
You can't attach/restore a 2008 R2 database to a 2008 instance, period. Though there are several workarounds (that also apply for attaching 2012 -> 2008, 2008 -> 2005, 2008 R2 -> 2005, etc). You can either upgrade the engine you're trying to connect to up to 2008 R2, or you can extract the schema / data from the database using generate scripts wizard, import/export data wizard, SSIS, or 3rd party tools like Red Gate SQL Compare (for a full list of alternatives see this blog post).
This comes up extremely often, did you search for "sql server version 661 655"? I came up with a whole bunch of hits using this search term and some slight variations, all on this site and dba.SE:
Failure attaching SQL Server 2008 database to SQL Server 2005
Cannot attach 2008 R2 database to 2008 instance
Database restore error
Create Database in SQL Server 2012, Script and Use in 2008?
Cannot restore backup on SQL Server Express
How to automatically restore a SQL Server 2008 R2 backup file
Database "cannot be opened because it is version 661" when attaching .mdf file
Use database 661 version with SQL Server 2008
SQL Server: Attach incorrect version 661
https://dba.stackexchange.com/questions/21525/restoring-an-sql-server-2012-mdf-to-sql-server-2008
https://dba.stackexchange.com/questions/20588/restore-sql-server-2012-backup-to-a-sql-server-2008-database
If you are developing .NET based apps in visual studio 2010, then they will typically support all versions of Microsoft SQL Server. That does not mean you install SQL server INSIDE of visual studio, just that you can connect to a SQL Server instance running somewhere.
If you are asking "Where can I get a copy of SQL Server that my university is using?", that depends. For development, you can use a SQL Express installation on your local machine that matches the major release of SQL (2005, 2008, 2008R2, 2012), or you can request the university (or someone else) grant you access to an existing SQL instance.

I have SQL Server 2008 R2 installed (shows that splash when I open Management Studio) but DB engine is 2005 express?

I am trying to restore a backup of a SQL Server 2008 database - but my engine is SQL Server 2005 Express. When I try and choose a different in the Management studio login, there is nothing BUT my SQL Server Express.
Now I am getting the RESTORE HEADERONLY is terminating abnormally on a 4+ GB DB that I need to restore.
Has anyone seen this? I am sure I installed SQL Server 2008 R2 (that's why I see it when I open the Management studio) ...so why do I only have SQL Server 2005 Express engine?
Thanks!
todd
It sounds like you only have the SQL Server 2008 R2 client tools installed. You will see the SQL Server 2008 R2 information on SSMS, but that doesn't indicate whether any server is installed.
I assume that SQL Server 2005 Express was installed already.
Of course, as you're seeing, the restore of a SQL Server 2008 backup will fail on the 2005 Express server.
You will probably have to install SQL Server 2008 R2 server again to get it installed. There are certain minimum requirements to install the server. I'm not positive, but I think if your computer doesn't meet the requirements, the install will automatically install client tools only.

SQL Server Express 2008 database compatibility with SQL Server Express 2005

a) I am in the process of developing a web site using the new free web development tool - Webmatrix (Beta 2) from Microsoft.
b) Web Platform Installer (recommends and also) automatically installs SQL Server Express 2008 along with Webmatrix and VWDE 2010 Express.
c) My database is created in SQL Server Express 2008. But the hosting company says that they would support only SQL Server Express 2005 (but not SQL Server Express 2008).
d) Can I go ahead with this hosting company or should I look for somebody who supports SQL Server Express 2008 specifically? In other words, the crux of the issue is:
Is it possible to open, read, update the database and tables created using SQL Server Express 2008 in SQL Server Express 2005 edition also?
Esh
I had the similar issue with hosting company.
They gave me a bak file from SQL server 2008 and I tried to restored in in my SQL 2005 environment and it consistently failed. Quite surprised to see the lack of backward compatibility. I would advise to go with hosting provider who supports 2008 or you migrate your DB to 2005.
In one word: NO.
SQL Server is never backwards compatible - if you have a database in a 2008 version, there is no way to restore and use that on a SQL Server 2005 machine. There's no trick, no third-party tool, no hack, nothing - it just doesn't work. EVER.
So if your hoster supports only SQL Server 2005 Express, you need to uninstall 2008 Express and manually install 2005 Express on your dev machine.
Or find a hoster that support SQL Server 2008 Express.

upgrading tfs 2008 sp1 to use sql server 2008

I have an instance of tfs 2008 supported by sql server 2005. I want to change the sql server machine by doing a restore based move. I also want to change the version of sql server to 2008.
I know that i can restore backups from sql 2005 to sql 2008, IN GENERAL, but I don't know if this is a thing that is OK for tfs databases.
I also know that sql server 2008 is supported by tfs 2008, but in this case when I have done an upgrade I am assuming that I should change the database compatibility mode to be "2008".
So, any advice on doing a sql server upgrade for TFS 2008?
Backup databases and report server key
Start downtime
Upgrade SQL2005 to SQL2008; AT will stop working at this step
Apply VS SP1
Apply TFS SP1; AT will work again
Apply SQL2008 SP1
Verify full functionality
End downtime