Has anybody had any experience migrating a BizTalk 2006 server from a SQL 2000 server to a SQL 2005 Server? I understand that nothing changes as far as the content of the databases - views, stored procs, etc. all remain the same. The scheduled jobs have to be migrated. All of that aside... tips, trick, etc.
I'd start with "Moving BizTalk Server Databases" in the BizTalk documentation
Related
We are on BizTalk 2013 Enterprise, we just noticed that the SSO database was accidentally deployed to SQL Server 2008 instead of SQL 2012 (where all other databases is), question is can we just take the database from SQL 2008 restore it on SQL 2012 and update BizTalk management database to point there instead of reconfigure BizTalk, redeploy and risk the application outage? Thanks
Yes.
You would follow the procedures documented here: Moving BizTalk Server Databases
In your case, you would only move the SSODB and follow the restore instructions for SSODB only.
In my firm we need an upgrade and so we decided to upgrade our system. We have now an SQL Server 2000 IIS 5.0 and .Net version 2.
I have also also asp.net api that written also with vs 2000 with .net version 2 that connected to the server. The api is very simple and there no complex query to the server.
the upgrade we will do will transfer our system to server 2012 IIS 8 and because we will upgrade also our vs (2010? 2012? whats better?) the .net framework will update as well.
The migration itself between the databases will do a dba (I know he need to transfer the database first to 2005/2008 and only then to 2012) my job is to make sure the API will work.
Can you name all the things I should take care of them on the api side before the upgrade
(if there lack of information ask and I will tell)
Here are some topics you may want to go through:
MSDN: Breaking Changes to Database Engine Features in SQL Server 2012, Discontinued Database Engine Functionality in SQL Server 2012, Behavior Changes to SQL Server Features in SQL Server 2012
If your app uses any of the functionality that had changed you will need to make necessary changes to make it work smoothly in the new environment.
Also checkout the following link:
Migration guide from Dell
I am dealing with a weird problem in SQL Server 2008.
I previously had SQL Server 2005 installed on my local machine.
I have a backup of a SQL Server 2008 which has to be worked upon locally and then restored to the original database (work involves use of ad-hoc queries which is disabled on my server since it is hosted with an ISP.)
Problem:
The SQL Server 2008 is giving me the following error.
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
The media family on device 'D:\Data\F1\purt144_634889883032976839.bak' is incorrectly formed. SQL Server cannot process this media family.
RESTORE HEADERONLY is terminating abnormally. (Microsoft SQL Server, Error: 3241)
Questions:
Can 2 or more versions of SQL Server co-exist on same machine? If yes why is the server instance showing version no 09.XXX (in the right hand section for SQL Server Management Studio 2008) version for SQL Server 2008 being 10.XX.
What could possibly be the problem apart from database being corrupted or backward compatibility issues?
Thanks.
Yes, you can have many instances of the same or of different versions of SQL Server installed on the same machine; so you can have one or more instances of SQL Server 2005 along with one or more instances of SQL Server 2008 (or of any other versions of SQL Server).
0 (zero) or one of these instances will be the default (or unnamed) instance and all the others will be named instances.
When upgrading from SQL Server 2005 to SQL Server 2008, depending on the options chosen, an existing instance (possibly but not necessarily the default instance if it exists) could have been upgraded from SQL Server 2005 to SQL Server 2008 or a brand new instance of SQL Server 2008 could have been installed alongside.
You should check the list of services to see the list of instances that you have on your machine. The SQL Server Configuration Manager that came with SQL Server 2008 will show you that under the SQL Server Services node.
The one with the name MSSQLSERVER will be the default or unnamed instance because you can connect to it without specifying its name. All the others will be named instances.
I'm currently developing a web application using SQL Server 2005, ASP.Net MVC, ASP.Net SQL Membership Provider (for authentication and authorisation), and Linq to SQL. Everything works great and is running as planned in the development environment.
However, the production environment has a SQL Server 2000 installation, and we are unable to obtain a copy of SQL Server 2000 to use in development.
Upon deploying the web application to the the production environment, what options do I have for migrating the database (schema + data) from 2005 to 2000?
You should make sure that your database compatibility in your development system is set to SQL Server 2000, and then consider using a tool such as the Redgate toolbelt for scripting out your schema and data for deployment.
Well, you could use the Database Publishing Wizard to generate a script of your database to SQL 2000 format.
We have an ASP.NET application written in Visual Studio 2003 (c#) using SQL Server 2000 as database. It’s an old web application that our clients have been using for 4+ years.
Now, we needed to upgrade the application to work on Windows Server 2008 using SQL Server 2008, both 64bit, both on the same machine. So we ported the application to Visual Studio 2008, made some needed modifications and successfully installed the application on Windows Server 2008 with database still being the old SQL Server 2000. Everything worked fine. But as soon as I modified the connection string to work with the new SQL Server 2008 64bit, it stopped working. Basically the web browser just shows – The webpage cannot be displayed; no error messages whatsoever.
I monitored the processess and event log - basically it seems that asp.net worker process is generating errors until it stops working. And I can’t figure out why. All should be fine on SQL Server 2008 side, all protocols enabled, even disabled firewall; i can connect to the instance using Management studio from the same server (64bit) and from other development machines (64bit/32bit).
Then i tried using the web application from my development machine (still Vistual Studio 2003 one, i.e. 32 bit with ASP.NET 1.1) and connect to the new SQL Server 2008 and i got „Server application unavailable“ error. Same thing happens, worker process is generating errors until it stops working.
I used IIS Diagnostic Tool to debug the moment the error occurs – all i got was basically unlimited numbers of „First chance“ exceptions (problems with msvcr80.dll, mscorwks.dll). If I limited the number of those, I also managed to get „Kernel32!TerminateProcess“ exception, which after analysis stated that it didn’t detect any problems with that; only one time i got the warning, describing that 1 client connection was executing for more than 90 seconds.
I dont think the problem is on the 64bit Windows server 2008 or SQL server 2008 side, since when, just for checking, we used Sharepoint application with the new SQL Server 2008 as database, it connected just fine.
So what am I missing with our ASP.NET application configuration/development that it cannot connect to 64 bit Sql server 2008?
Thanks and regards,
Martin.
This sounds like a configuration problem, probably a permissions problem. Your Sql Server is on a different box than the your web server? If so I would look at what user your web site is running under. Make sure that user has access to the Sql Server.
If your user does have access make sure it has access to travel the wire to your SQL Server. Try to connect to the SQL Server via Sql Management Studio with the user's credentials.