I am new here. I was recently handed a project to create an environment with Windows 2012 and SQL Server 2012. The goal is to take the existing databases in our current environment which is SQL Server 2005 and Windows 2003 platform. I have tried looking for specific whitepapers to doing this or checklists that might exist. What are some of the things I should plan for, can I de-attach a database in the SQL Server 2005 environment. I did check the compatibility version for SQL Server 2005 environment is 90. Any help would be appreciated. I feel as if I might be in over my head.
I don't recommend the De-attach/attach method. De-attach/attach method will only work with the database but you will have to manually create the jobs. There will be other issues.
Related
After install I wanted to practice creating SQL Server Agent jobs, I know that you cannot do this on a SQL Server Express instance, so I'm wondering with my developer edition if it's possible to create a non-SQL Server Express instance, and if so how, thanks.
Please check following tutorial which shows SQL Server 2016 installation step by step
In general for all SQL Server versions the setup procedure is very similar.
You can exclude installing components like Reporting Services, Integration Services, Analysis Services and other optional components if you want to make the setup process simple
What you should install is Database Engine Services! You can exclude the other features under Database Engine if you check the screenshot I shared in the article.
And what is important is the Management Tools that you can use to connect db instance and execute queries, etc.
Although the above tutorial shares the download link, you can also refer to https://www.microsoft.com/en-us/evalcenter/evaluate-sql-server-2016 for SQL Server 2014 and 2012 download links as well
So I realized that I only had SQL Server 2012 Express edition by using:
SELECT SERVERPROPERTY('EDITION')
Using the link provided by Eralper I installed SQL Server 2014 developer edition and now have two instances of SQL Server, one is the the express for 2012, the other is the 2014 developer edition. Once I log in to the named instance I can finally see of course the SQL Server Agent node at the bottom.
Thanks everyone for all the help and sorry for the confusion.
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.
I was wondering if we could backup the database that we currently host on regular SQL Server, and put it onto our clients computer when we setup SQL Server Express for them.
Is this possible?
Thanks,
Matt
Yes, it's possible to restore a database backup from the Standard edition to the Express edition. It's not possible to restore a SQL Server 2008 to a SQL Server 2005 version, though.
However, there a some minor differences between versions. I've noticed an issue in SQL Server Express 2005 when calling .NET SQL CLR functions across databases, so your mileage may vary. I haven't been able to find a good overview of the exact differences between the various SQL Server editions.
It's always best to keep the development platform as close as possible to the release platform. I can only recommend that you use the Express edition of SQL Server for development as well; and re-test your application.
Some SQL Server 2005 and 2008 questions.
1) Can they coexist on the same Windows 7 machine without issues?
2) Can you attach and run 2005 databases to SQL Server 2008 without compatibility issues or is this a no go?
3) Does SQL Server 2005 even work on Windows 7?
Yes, both can coexist on the same machine without issues.
Yes, however, once you attach a 2005 database into a 2008 instance, you have upgraded it to 2008 never to go back to 2005 unless you export the data into some universal format. You can however, have both engines running simultaneously and can use either set of management tools to see either database (although some features will only work with the 2008 management studio working against the 2008 database)
Yes. Both sets of tools (including Management Studio) and services can coexist on the same machine (I have this very setup). The only thing you cannot do is to have both engines listening on the same port. Thus, one of the two will have to be a named instance.
1) Yes.
2) You can view 2005 database under 2008 management studio, not sure about hosting them under a 2008 instance though. I'm fairly confident they do, but not sure if it's native or via converting to a 2008 database.
3) Yes.
Note that you can't have 2005 MS and 2008 MS (management studio) installed on the same OS. This was based on my experience a long while ago when 2008 first came out, I got an error message stating that I couldn't install it because of a previous version (2005) being installed, or something akin to that. Turns out it has changed.
I'm wondering if anybody has had any experience in trying to install SQL Server 2008 Express along side with SQL Server 2000. We have a production server running 2000 which all of our current stuff is running on. However, something new is in the pipeline that uses SQL Server 2008 Express.
Hitting Google thus far has given me nothing concrete. There was an obvious no from a preview release of 2008 but nothing about RTM 2008.
I could try installing it but would like to find out as much as I can before doing so. I can see the 2008 install failing, eating 2000 in the process.
The alternative paths that I have include having the 2008 db be turned into a 2000 format (which I'd like to avoid as we only have a 5 connection licenses) and building a new server (we already have enough and it seems overkill). Redoing the 2008 DB is viable as it doesn't use any new whiz-bang features from 2008.
Virtualization can be an option as well, but it's not quite in our cultural yet.
Any insights here will be appreciated.
Keith
yes you can, you have to make the 2008 version a named instance if the 2000 version is a default instance