we are planning to move biztalk database from one place to another as well as upgrade the sql server.
the initial database is in sql server 2008 R2 and target is sql server 2012.
but the thing is that we have to set up database on another system,
i tried to search it on msdn but they are providing reference to upgrade from 2005 to 2008 , or moving database from one server to another.
do you think that will work in my case !!
i found this article.http://msdn.microsoft.com/en-us/library/ee378547%28v=bts.10%29.aspx
relating to upgrading as well as moving..
but this is quite older one.
how can i upgrade as well as move biztalk database from sql server 2008 R2 to sql server 2012 on a different system (side by side upgrade).
do i have to follow same steps as upgrading a normal database from sql server 2008R2 to sql server 2012 or some other one ??
As long as the SQL Server edition (2012 in your case) you are migrating to is supported by your BizTalk Server edition, you can follow the procedure to move BizTalk databases.
You can check the version compatibility here.
Related
I have tried to upgrade SQL Server 2008 R2 (Which has 4 databases) to SQL Server 2012. During the upgrade, the upgrade program hung up and got killed. Now I have a database at version 698 which is neither good for 2008 R2 nor 2012. Unfortunately this is the only database with a backup 6 months old (so restoring a backup is not an option as we would lose 6 months of development). When I attach to 2012, it cannot continue from version 698. When I attach to 2008 R2, It is attached fine but cannot read any objects in db
Please advise.
I have been using this connection string with no problem on a number of databases and MS operating systems. Windows Server 2003, 2008 R2 and 2012 R2 Eval, all Express versions.
I am now trying to deploy to a new Windows Server 2012 R2 installation and I am getting some errors. I have the SQL Server 2008 R2 installation on the Windows Server 2012 R2 machine.
My con string:
connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\myDB.mdf;Integrated Security=True;User Instance=False" ProviderName="System.Data.SqlClient"
I think this must have something to do with the installation sequence of the components on the new server.
I have in the past been able to simply copy myDB.mdf to basically any web server and open or access the DB tables. This DB includes an ASP membership for the web site that it is tied to.
Here is the error:
CREATE DATABASE permission denied in database 'master'. An attempt to
attach an auto-named database for file
C:\inetpub\techTran\App_Data\myDB.mdf failed. A database with
the same name exists, or specified file cannot be opened, or it is
located on UNC share.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: CREATE
DATABASE permission denied in database 'master'.
I thought I understood what this error was. I have checked permissions and they match the other servers where this database has been deployed. My SQL Server installations are basically all the same. The only difference here is that this is Windows Server 2012 R2 on a VM. Or I did not install the SQL Server 2008 R2 the same way I have done in the past 5 servers I have set up. (Which I am guessing is probably the case.)
UPDATE: Uninstalled and reinstalled SQL Server and SSMS.
I know there is only one database name on the server called myDB.mdf, so I don't believe the "same name" portion of error. I have added security to the db so that it can be opened and I even installed Visual Studio 2012 on the server to be certain that the db could be opened. I can run the full app on the localhost (server 2012) but I can not access it over a web connection.
I believe the specific error message relating to
CREATE DATABASE permission denied in database 'master'
is the issue.
I have never seen this error before.
I typically assign NETWORK SERVICE account to the database to allow access and this is how this one is set up as well. I also thought this might be a connection string issue. But this same string has worked on 4 different servers now with no changes. Server 2003, 2008 R2, and 2012 (demo platform)(all Express versions), now in production this is failing.
The home page loads and then the login throws the above error.
Your connection string says AttachDbFilename=|DataDirectory|\myDB.mdf. Well, your path must have changed in one place (SQL Server) and not the other (app configuration). AttachDbFilename will try to create a new DB if it can't find that file. That's probably your error.
As an aside, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 all have differences, especially with security and in particular with how SQL Server behaves, but you keep using them interchangeably. That makes it very confusing to tell what's going on. Also, your connection string says Data Source=.\SQLEXPRESS. Is this SQL Server Express? Because that has important differences with most other editions of SQL Server, too. More recent editions are very similar to Standard edition, but the older the edition, the more quirks it has. They're generally considered different beasts.
SOLVED: I am not sure how this happened or perhaps why it didn't happen. But for some reason the installation of SQL did not add the NETWORK SERVICE account to the sysadmin Server Role. I cross referenced this with the SERVER 2003 installation where SQL 2008 R2 is also running, and discovered that the sysadmin SQL Server Role included NETWORK SERVICE in my correctly functioning environment. So once I added the user account to this role, everything came up fine.
I believe this might have been an issue during the installation of SQL 2008 R2. I did specify NETWORK SERVICE, but for some reason it was not provided the role.
Has anyone connected Adempiere (ERP) (or any PostGreSQL db) to SQL Server 2012 Express?
There used to be an IT manager to help me out with this, but now i'm left alone with this.
I downloaded the free Sql Server 2012 Express and wanted to use the SSRS for Adempiere. It seems its running on the SQL Server 2010 for SSRS.
I have already added the ODBC Data Sources for 32 Bit. My computer is using 64bit, is there any incompatibility? I'm not sure if my server is 32 or 64bit.
I've tried following the instructions on http://postgresblog.blogspot.com/ but to no avail.
I already have Crystal Report running, so i'm sure its possible to run 3rd party software for Adempiere.
Anyone knows how i can use SSRS for Adempiere? Thanks!
Since you're using Express edition, if you're trying to connect to any Data Source other than an database on the same SQL Server instance it won't work.
See Features Supported by Reporting Services in SQL Server Express.
From that article:
Report data sources must be SQL Server relational databases that run
locally in SQL Server Express.
Also:
Analysis Services, Oracle, XML, SAP, SQL Server Integration Services
(SSIS), OLE DB, and ODBC data sources are not supported.
You're going to need a different edition to connect to an ODBC Data Source.
I am using SQL SERVER MANAGEMENT STUDIO 2008 R2. I have used my pc's name(For example, MY-PC) as a server name to make databases. Now how can I get the database I created in my pc's named server, when I select .\sqlexpress as a server.
The error it shows when I tried to restore in .\sqlexpress from .bak file:
Restore failed for Server 'MY-PC\SQLEXPRESS'. (Microsoft.SqlServer.SmoExtended)
Additional Information:
System.Data.SqlClient.SqlError: The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.2531. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. (Microsoft.SqlServer.Smo)
You can't restore the database in the above scenario - as per the error, the backup was taken on a SQL Server 2008R2 instance, and you are trying to restore it on a SQL Server 2008 instance - backup files are not backwards compatible.
You can see this from the error message:
10.50.1600 is SQL Server 2008 R2 RTM
10.00.2531 is SQL Server 2008 Service Pack 1
See the following Microsoft article for details on SQL Server version numbers:
http://support.microsoft.com/kb/321185
I have been using SQL Server 2000 for a few years. For the deployment of SQL Server 2000 I was using MSDE (Microsoft Desktop Engine 2000) on target machine.
Now I have switched over to SQL Server 2008 R2. I have develop an application by using SQL Server 2008 R2 as my database. Now I am confused about the deployment of this app.
I have searched for MSDE 2008 R2 but could not find it. Will anyone please tell me that what should I use in the place of MSDE 2000?
The replacement for MSDE as of versions 2005 and newer is SQL Server Express.
See more about SQL Server 2012 Express here.
You can also still download the SQL Server 2008 R2 Express version here