I have been browsing for an answer from last one month.
Now I could not resist myself to post it here and discuss my observations with experts.
Please find my observations/doubt:
I am using SQLOLEDB and SQL Server 2008 R2
As per MSDN, The commercial release of Microsoft SQL Server, codename "Denali"(SQL Server 2012) will be the last release to support OLEDB.
Reference : MSDN BLOG
On the other hand it is mentioned that the OLEDB data consumers are supported till SQL Server 2014
Reference : MSDN Reference
Now I need to upgrade my tool to work with SQL Server 2012 and all of the later version.
However I checked my application with SQL Server 2012 and found working fine without changing anything.
So not sure how it is working and which announcement shall i follow and shall i change my code and
switch to other DB access methodology(SQL Native, ODBC)
Any suggestion will be really helpful.
Many Many Thanks in advance.
Few more link on Stack overflow itself : Stack overflow link
SQL Server 2012 is the last version to support SQL OLE DB connections. So, if you're on SQL Server 2012, then you're still fine.
For future versions, Microsoft gives this article to convert your application from OLE DB to ODBC - https://msdn.microsoft.com/en-us/library/hh967418.aspx
Related
I am going to do a customer SQL upgrade and they currently have SQL Express and I want to upgrade it to Microsoft SQL server 2008.
Will it be okay to restore the SQL Express backup to Microsoft SQL Server 2008?
First off, the comments seem to mention MySQL. I can see that you edited it to say SQL Express. If it is indeed MS SQL Express then yes, as SMM said it will work.
I have done this a few times before, and it worked just fine. Though rather than a backup/restore I would move the .mdf file.
This is done by detaching the DB from the Express instance and attaching it to the Server 2008 instance; this can be easily done via sqlcmd or the Studio Manager. The steps can vary based on systems(s) setup. As such, I did a google search to see if there existed a step by step guide for this rather than typing a bunch of scenarios as shots in the dark. There are a plethora of them:
I just Googled: move sql express .mdf to sql server 2008
I also found this and it would seem to be a good match for your situation and has good information:
http://www.mipsis.com/help/Moving%20SQL%20Express%20Database%20to%20SQL%20Server.pdf
Let me know how it goes, and if you need specific assistance with the process please follow up.
I have done SQL Express to SQL 2000 and SQL 2005 successfully in the (distant) past. I am sure this will work. I don't remember any specific caveats other than making sure that you don't try to go from a later version of Express to an earlier version of SQL.
A database that was originally from SQL Server 2008, was restored into SQL Server 2012. A backup from SQL Server 2012 was made and I am trying to restore it on my local SQL Server 2008 Express. However I get an error 'Specified cast is not valid' (SQLManagerUI).
I have generated an SQL Script from 2012 and set it so that it will generate with compatibility to SQL Server 2008. However it is a large sql file, around 700mb.
I recall before that I had tried to run a script of that size before on my local SQLExpress and also got an error.
Is there a way I can get a "large" database from SQL Server 2012 into SQL Server 2008 Express?
Thanks to Marc and Aaron for providing the answers.
The quick answer is no, it's not possible to restore a backup file from a higher version to a lower version of SQL Server.
A work around would be to generate the scripts to create the database.
You can target the script generation to a lower version.
Please see comments above for more information.
Links:
Why an SQL Server Database from a higher version cannot be restored onto a lower version of SQL Server?
Create Database in SQL Server 2012, Script and Use in 2008?
Couple things to add that might be helpful to folks
When scripting large databases using scripting wizard in SSMS it’s really important to check the execution order and be willing to re arrange it manually. Older versions of SSMS had this problem because they (probably) relied on sp_depends that has a bug.
What I’ve found really useful in such cases are tools like ApexSQL Diff that you can use to read database backups and generate scripts that are in correct execution order.
SQL Server database backup restore on lower version
One thing that none of the methods will catch is the thing Aaron mentioned about using functions specific to higher version.
A better option than using the SSMS scripting wizard is to use a similar tool available on Codeplex called SQL Database Migration Wizard - http://sqlazuremw.codeplex.com/releases/view/32334. You want the latest version v4.x to work with SQL Server 2012.
The tool is originally intended to be used for migrating databases between SQL Server and Azure. However the tool works just as well as between SQL Server and SQL Server. The trick is to set SQL Server rather than Azure as the target in the advanced options.
The reason this is a better option than the SSMS scripting wizard is that it uses BCP for the data transfer rather than TSQL and so is much more efficient.
Where to find the information about service packs already released or planned for SQL Server 2008 R2?
SQL Update information, for all versions, all types (Service packs and the monthly cumulative updates) is published at...
http://blogs.msdn.com/b/sqlreleaseservices/
I believe that only Cumulative Updates are released for the SQL 2008 R2.
The current SQL Server 2008 SP is SP2, but it does not apply to R2.
R2 is a separate release.
If you go towards the bottom of this KB article it is updated with the latest SP/CU for each version of SQL Server as it is released. It doesn't give a link to the KB but it is a good central point to check.
New: Microsoft has created an update center that will show the latest SP/CU currently released with a link. I'm not sure how quickly they will update this though, example being that they don't show SP1 for SQL 2012 on there yet.
I'd try the Internet. Surely this is a simple thing to google?
My company is planning to migrate it's intranet/internet based ERP to the latest form of MS SQL Database available.
Presently we are using SQL Server 2000 Professional.
And we are planning to shift to SQL Server 2008 Web edition.
Please tell me whether this is the right step and whether it is feasible or not.
Thank you in advance.
"Please tell me whether this is the right step " - that's something you and your company need to decide.
It is feasible, and in the majority of cases straight forward.
Your first step should be to run the Microsoft SQL Server 2008 Upgrade Advisor
Microsoft SQL Server 2008 R2 Feature Pack contains the Microsoft SQL Server 2008 R2 Upgrade Advisor
Formulate and test a rollback plan
Determine your upgrade window and acceptable downtime.
Ensure database consistency: Run DBCC CHECKDB on databases to be upgraded to ensure that they are in a consistent state before performing the upgrade.
Back up all important files: Back up all SQL Server databases from the instance to be upgraded (including master, model and msdb), data and transaction log files, as well as any application files, script files, extract files, etc. so that you can completely restore them in the event of a failure.
It's both feasible and easy. The path from one version of SQL Server to another is usually pretty simple. Do you have any special stored procedures or reports generated in SQL Server that need to be rewritten/re-imported?
As far as right step - the question is, Why? If it's working, do you really need to mess with it?
If it's for intranet (some app for your internal usage) then consider using SQL 2008 Express edition. It's free and you can use it as an instance running along the full 2000 version. That way you will have some extra features from the full version.
But you have to know that applications running on SQL 2000 may not work on 2008 and they are even more probable not to work on 2008 R2.
What can you do in SQL Server 2008 Standard Edition that you cannot do in SQL Server 2008 Web Edition?
I've seen the Microsoft feature lists, but I am wondering from a very practicle standpoint where I am going to run into limitations.
Have you seen this matrix as well?
http://msdn.microsoft.com/en-us/library/cc645993.aspx
From what I can tell Web excludes a lot of the more advanced features, especially those related to development and data mining, but nothing that would stop you from using it for a non-enterprise web site's data source. It seems to be between the Express version and Standard version.
One of the biggest limitations is that it can't be a publisher for SQL replication. If you want to have multiple database and replication data between them, then you need at least one SQL server to be Standard or Enterprise to act as the publisher.
http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx
Edit: Sorry, you've probably already looked at the above.