Microsoft SQL Server Management Studio (2012) - ssms

Here is the image that pop ups
Microsoft SQL Server Management Studio (2012)
I hope someone can help me with SSMS, because I can't create table even though I can connect.
Showing this error message every time I try to create table
TITLE: Microsoft SQL Server Management Studio
This backend version is not supported to design database diagrams or tables. (MS Visual Database Tools)

The error is literally telling you the problem here, the version of SSMS you are using (SSMS 2012) does not support the back end version that you are using (SQL Server 2019). I can tell it's 2019 because in the top left of that image it has Version 15......
The first version of SSMS to provide support for SQL Server 2019 was SSMS 18.0, which was release on 2019-04-19.
What's new in 18.0
New item
Details
Support for SQL Server 2019
SSMS 18.0 is the first release that is fully aware of SQL Server 2019 (compatLevel 150).
Support for SQL Server 2019
Support for "BATCH_STARTED_GROUP" and "BATCH_COMPLETED_GROUP" in SQL Server 2019 and SQL Managed Instance.
Support for SQL Server 2019
SMO: Added support for UDF Inlining.
Support for SQL Server 2019
GraphDB: Add a flag in showplan for Graph TC Sequence.
Support for SQL Server 2019
Always Encrypted: added support for AEv2 / Enclave.
Support for SQL Server 2019
Always Encrypted: connection dialog has a new tab "Always Encrypted" when the user clicks on the "Options" button to enable/configure Enclave support.
You need to update to a version of SSMS that supports the back end version you are using. Personally, I would suggest updating to the latest version, which is currently 18.9.1.

Related

how do I change Microsoft Sql Server Studio 2022 from rtm?

I recently downloaded ssms 2022 but it refuses to accept connections, make diagrams, giving comments, relations, give design view of the table, etc. the software is upto date and it keeps giving errors like the back end doesn't support. How do i go about this, have tried using both express and developer edition and face the same problem. it says both versions are rtm.
a solution on how to make my ssms function effectively.
The SSMS version being older than the database version. you have to download SQL Server Management Studio (SSMS) 19 (Preview)
Download SSMS. It is now available and is the recommended version of SSMS for SQL Server 2022.
you could back to this link for more information.

SQL Server 17.4 Developer Edition Compatibility Levels

In SQL Server 2017 Express, v17.4, I am unable to select a compatibility level beyond 2008 (100). The only versions available are 2008 or older. I am training for the MCSA SQL Server developer exams and I want to test some functionality unique to SQL Server 2016 (130) but am unable to do so until I figure out this problem. I did do my best to search here and on Google, but I'm not finding even a slightest reference to this. Is it a limitation of using a free version of SQL Server? As an alternative solution, is there a way to download older developer edition versions of SQL Server that might contain 2016 DB compatibility?
You can download SQL Server Developer edition from Visual Studio Dev Essentials https://my.visualstudio.com/Downloads?q=SQL%20Server%202017
Or from here
https://www.microsoft.com/en-gb/sql-server/sql-server-downloads

SQL Server Database Vesion

I have a problem regarding a SQL Server database.
The error message is
Cannot be opened because it is version 852. This server supports version 782 and earlier. A downgrade path is not supported.
I tried everything, updating via Visual Studio 2015, downloading SQL Server 2016, installing SSMS, but nothing changed the server's version.
I need to somehow change the server's version so it will attach the the database successfully.
Please help!
You are attempting to attach SQL Server 2016 database files to SQL Server 2014. This is not supported.
Your only solution is to upgrade SQL Server from 2014 to 2016. Note, this is the database engine, not management studio.
Here is a list of all SQL Server internal database version numbers: http://sqlserverbuilds.blogspot.com/2014/01/sql-server-internal-database-versions.html

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.

Error: Can't attach DB to SQL Server 2012

I have SQL Server 2012 and I'm trying to attach a db which was previously used with SQL Server 2012, surprisingly I'm getting the following error:
The database 'DatabaseName' cannot be opened because it is version
706. This server supports version 622 and earlier. A downgrade path is not supported.
I don't really understand how this could happen since like I said it was used with same 2012 version. What am I doing wrong? How can I make it work? Please explain in detail how this can be resolved.
Thank you!!
The error sounds like the server you are trying to attach the database to is not SQL Server 2012. This may be the version of Management Studio / Management Studio Express you're using, but I suspect SELECT ##VERSION; will tell you something different. It may just be a connection string mixup if you have multiple instances of SQL Server installed, otherwise you should download and install SQL Server 2012 Express from here.
#source
It sounds like you had the following configuration and source databases:
SQL Server 2008 SP3 (ver 10.0...) - database engine
SQL Server Management Studio 2012 (ver 11.0...) - management tools
a database that was created with SQL Server 2012 (version 706)
As mentioned you could install SSMS for SQL Server 2008 (after you uninstall SSMS for SQL Server 2012). Then you would have to script your database for that version and re-run the script via 'Tasks>Script...', remembering to set the target server version as shown below.
After scripting you can then use the import/export wizard to export and then inport the data into the new (downgraded database), assuming the database had no 2012-only datatypes (such as sequences).
Another consideration is database compatibility level as shown below. You can have a SQL Server 2012 instance which hosts databases with various compatibility levels.
Using SELECT ##VERSION works very well for me. Your Database Engine is connected to a 2008 DB which certainly doesn't allow you to attach. Once I change my Database Engine to connect to 2012 DB, it works for me.
Check your Database Engine connection. You can be working on 2012 Management Studio yet connecting to 2008 DB. This is what happened to me and I have solved it use SELECT ##VERSION.