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.
Related
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
As I'm learning the ins and outs of ASP.NET user management, I've learned that the default in VS is for it to use a SQL Server Express .mdf file for the data it needs to save. This won't help me for when I deploy my site, as I'm running SQL Server 2008 R2 on my IIS 7.5 server. I know that I can run a command line tool to automatically create the db tables necessary for user management, and will do that on my development machine, but how do I tell my existing, in development code in VS to ignore the existing Express .mdf file and look at the newly created db tables?
Simply update your Web.Config to set up the role provider and the database connection string:
http://weblogs.asp.net/scottgu/archive/2006/11/20/common-gotcha-don-t-forget-to-clear-when-adding-providers.aspx
http://www.codersbarn.com/post/2008/02/24/ASPNET-20-Guest-Book-Admin-Part-II.aspx
Also, Scott Mitchell's Membership and Roles tutorial series is the most comprehensive I've seen:
http://weblogs.asp.net/scottgu/archive/2006/05/07/ASP.NET-2.0-Membership-and-Roles-Tutorial-Series.aspx
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.
I'm trying to create a database within the app_data folder of an asp.net mvc project using the IDE, but i am getting a "Required Components Missing" message indicating "Connections to SQL Server files (*.mdf) requireSQL Express 2005 ....."
I am using
- Windows 7 Enterprise
- VS2008 Team System SP1
- SQL Server 2008 Developer Edition SP1
I have altered the database connection to use the default instance by setting to blank using
Tools -> Options -> Database Tools -> Data Connection : SQL Server Instance Name
I also note from the SQL Server Books Online that the user instance feature will be removed in the future, but for now it suits my effort in developing an application where a number of people are working on the project.
Has anyone managed to create a database in the same manner?
It appears Nerd Dinner has done so
The attached user-instance database in the App_Data will work only with a SQL Server Express edition - 2005 or 2008.
It does not work with a full SQL Server edition, like Web, Workgroup, Standard, Enterprise or Developer. It does not - no way - no trick to make it work - does not - period.
If you want to use that mechanism of attaching a user instance database in your App_Data folder, you must use SQL Server 2005/2008 Express.
Ok! I'm ready to embark on some .NET development for the first time.
I've recently installed Microsoft Visual Studio which included Microsoft SQL Sever 2005.
What is the prefered method for programming against a development database? I want to write an ASP.NET application that uses a database and I'm not sure how to create one. In my start menu for SQL Server 2005 all I have is:
SQL Server Configuration Manager
SQL Server Error and Usage Reports
SQL Server Surface Area Config
I don't see an intuitive program to create and design databases on that list, so how do I do it?! Will I be creating a full fledged SQL Server database or a "flat-file" fake database to program against?
Can someone please tell me what is up on creating my first MS SQL Server 2005 database?
If you've Visual Studio, just goto server explorer, Add a new database connection to your database, and start off.
Or, create a new website project in Visual studio, right click the App_Data folder->Add New Item and add a SQL Server database mdf file, which will be attached to the sql server when you run the app. You need to deploy the mdf file when doing a production release :)
You might want to watch the videos in ASP.NET website http://www.asp.net/learn/
Otherwise, consider using Microsoft SQL Server Management Studio (an express edition is also available).
You are looking for Microsoft SQL Server Management Studio Express. Its pretty easy to add a database once you get your head around it.
To be clear, the SQL Server included with Visual Studio is an express edition. However, the one thing it is lacking is the SQL Server Management Studio (Express). I'd download and install the express edition that included the management studio (note that VS 2005 and 2008 include SQL Express 2005, you can use either SQL Express 2005 or 2008 for your purposes).
You can create a new database and do everything you need to from within the VS IDE but you'll probably find the SQL Management Studio environment much more intuitive and simpler to use as a beginner.
A quick note on SQL Express - Microsoft doesn't suggest it for 'production' environments due to limitations placed on the amount of RAM that Express can see/use and a few other factors. This is one of the few cases in which I agree - if you're doing anything complex that involves large databases or dozens of users then invest in MSSQL Workgroup Edition at least, or for Enterprise projects use MSSQL Standard or Enterprise versions.