I recently installed BizTalk Server Dev 2010.
As part of installation, new databases are created and some services are also added.
Because I am currently NOT working with BizTalk Server, I want to stop the service associated with it specially the one that connects to SQL Server.
I have already stopped these three BizTalk services:
BizTalk Service BizTalk Group
Enterprise Single Sign-On Service
Rule Engine Update Service
but not able to find the one that communicates with BizTalk SQL Server Databases.
I can still see BizTalk SQLs in profiler.
Any idea which other service I should stop?
Thank you!
There are also SQL Server Agent Jobs created to backup the database and keep the message box and tracking databases running. That is probably what you are seeing activity from.
Related
I'm about to deploy an ASP.NET web application for testing in production. Essentially, this is just a table that is linked to a SQL Server table/view that is obviously dynamic when the data in the tables are updated.
I have a hosting plan with a site that I'll be pushing the files to, which includes a SQL Server database in the hosting plan. I also host a SQL Server instance on the network.
My question is, what is the standard way of dealing with SQL Server in this deployment? I think I have the options below, but as someone who has only ever developed applications offline, this is new to me, so please excuse my novice ignorance.
Have the application connect via IP address in the connection string to my SQL Server instance, as specifying the server name (SQLDEVSRV01 for example) won't be on the "network" when it's sitting in the site's FTP. Am I to assume my connection string will only work on the network, and once deployed to a website, will cease to function unless connecting via TCP/IP?
Host the server on the web in the same site host location. So upload the site files to my website host and setup the SQL server there. Would I be able to just specify the Server name (SQLDEVSRV01 for example) in the connection string there, as whilst it wouldn't work in development as it wouldn't be on the same network, it would then work once deployed on the web?
Embed a SQL Server instance within the app using localdB or something similar to hold the background data. If this is the case, can the data be accessed from the backend, either using SSMS or some other method?
Essentially, my aim here is to have the web app retrieve the data live from a view/table hosted in SQL server, where the backend data can be amended, manipulated and updated independently of the app, so the app can just pull the data when refreshed.
The standard way of doing this is to deploy your database to the hosting providers SQL Server instance and then connect your app to it using a connection string with their details. As it is normally a shared instance you do not have to normally worry about having the SQL instance machine patched etc.
Personally I would not be installing SQL Server myself unless I decided there was benefit to having an instance I wanted the control over nor would I be changing the structure or implementation of my application to suit a hosting providers setup.
We have existing Web application which has following layers
Web Layer (Asp.Net MVC ) Sql Server 2012 SAP ETL services: ETL
jobs pulling the data from different datasource to sql server
We have QA,STAGE,Production environment for the application.
We are planning to migrate the application to AZURE PAAS.For Web layer there is no issue's in migrating to PAAS.
For DB Layer we have used microsoft migration steps using visual studio there is no issues at data base design level.
the only concern moving DB to PAAS is SAP ETL service and application jobs which is dumping millions of data to database. Not sure about how many DTU's it will consume.
Just need help to decide for the above scenario is it good to move DB to PAAS or have Sql server VM ?
Thanks
I think it will be best for you to make some tests and base your decision on the results. For example, create an Azure Sql Server (Standard S0) and see how that performs. A great benefit of the PaaS offering, as you probably know, is that many aspects are handled for you automatically - upgrades, you can easily switch to another performance level, DB backups and restored, etc.
There is a very good article which can give you some additional pointers on how you can evaluate the pros/cons in your situation - Choose a cloud SQL Server option: Azure SQL (PaaS) Database or SQL Server on Azure VMs (IaaS)
I would personally choose the PaaS option. I have used Azure Sql Server for a long time and I never want to go back to configuring and supporting my own SQL server.
I've installed BizTalk 2013 Standard on a dedicated server. SQL is set up as an active / passive cluster (there are 2 virtual machines set aside for this) i.e. SQLDB1, SQLDB2. Now while configuring BizTalk, do I need to mention SQLDB1, SQLDB2 or cluster DNS name? If cluster DNS name, then how do I find this?
From Clustering the BizTalk Server Databases
Procedures for Clustering the Databases
Make sure you meet the following prerequisites before you start
clustering the BizTalk Server databases. When you create the domain
groups for your BizTalk Server environment, you must create global
domain accounts.
Configure the SQL Server cluster before you install and configure
BizTalk Server. For more information about clustering SQL Server 2008
R2, see Getting Started with SQL Server 2008 R2 Failover Clustering
(http://go.microsoft.com/fwlink/?LinkId=156820).
If you are also clustering the master secret server, configure that
server first. For more information about high availability for
Enterprise Single Sign-On, see High Availability for the Master Secret Server.
To run the BizTalk Server Configuration Wizard
Install BizTalk Server 2010 on a runtime server.
Launch the BizTalk Server Configuration program. Click Start, point to Programs, point to Microsoft BizTalk Server 2010, and then click
BizTalk Server Configuration.
To apply a custom configuration, follow the steps in Working with the Custom Configuration Manager
(http://go.microsoft.com/fwlink/?LinkId=156822) in BizTalk Server
Help. To specify the SQL Server cluster for the BizTalk Server
databases enter the name of the SQL Server cluster in the
Databases dialog of the configuration.
Complete the BizTalk Server configuration by following the instructions in Custom Configuration
(http://go.microsoft.com/fwlink/?LinkId=156823) in BizTalk Server
Help.
Launch "Cluster Administrator" on any one of the SQL Server nodes i.e. SQLDB1 or SQLDB2
Take a look at the SQL Cluster group properties and see what the "Network Name" is.
If you hadn't provided a network name prior to now, you should do so now.
This is the name you should use to connect to your SQL cluster. You could test this out using SQL Management Studio to be sure.
Best of Luck
I have a BizTalk Server 2010 installed in windows server 2008 R2. When i publish wcf service through wizard and try to run the service on browser, it returns an error :
The Messaging Engine failed to register the adapter for
"WCF-BasicHttp" for the receive location
"/OrderProcessingDescription/OrderProcessService.svc". Please verify
that the receive location exists, and that the isolated adapter runs
under an account that has access to the BizTalk databases.
Also account used in the application pool is a member of the BizTalk Isolated Host Users group.
One thing which is not installed in Windows Server 2010 is Domain Controller. Please let me know if I need to install it .
please see the following thread to check the actual error:
Link to thread
Answer from thread:
To solve this issue check the application pool security user account
in the IIS. Add that user account into the BizTalk Isolated Host Users
group. Or change the application pool to the pool which user is
already a member of the BizTalk Isolated Host Users Group.
The domain controller feature actually has very little to do with this and the feature is likely not to be installed on your BizTalk server.
Since you are using the publishing wizard:
Ensure that there is an app pool available which is linked to a BTS Isolated host account (you seem to have done this).
Ensure that the app/virtual directory created by the wizard in IIS for the basicHttp endpoint is configured to use this app pool.
Ensure that the corresponding receive port is created, and enabled (look in the BizTalk admin console).
Also ensure that the BTS host process for the receive port is running.
I can neither login from my application nor connect using the wizard to my Membership Provider on my local machine. My other DBs can connect from my application just fine. My connection string is correct, it has not been changed (I was able to login using membership previously, this is a new issue).
I created a new App to see if it could be the config, threw a login on it and registered and ran into the same issue.
This is the error message I am getting: "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) "
Though my other DB can connect I still checked:
TCP/IP enabled
Multiple connections enabled
Firewall down
Correct instance of sql server being referred to in Machine config.
Also, my network service account has rights to the DB, but should there be an ASPNET user?
I can't think of a single thing I have changed to this machine since this was working previously.
Thank you.
EDIT DETAILS: There are no aliases, yet, but if my other connections are working that shouldn't be the issue. I understand these things can be wonky though, so that's something I'm going to try now. Thanks. I will also try and take a look at what's going on while trying to connect. Best way: event logs?
I am using Windows Auth, I'm connecting locally, using Windows 7 and SQL Server 2008 along with VS 2008. I can connect with Management Studio and query the DB, yes. NetworkService account has rights to the DB.
Check the Server name in the connection-string if the Sql-Server is in the same machine with the web application use "."(dot) without quotes instead of the computer-name in your connection string.
Have you tried sniffing it to see if there's anything you can see on the wire when the connection attempt is made?
Are there any aliases around the server/DB name? Have you tried creating one and connecting to it?
Are the other instances you can connect to on the same machine? Same SQL Server instance?
If you use impersonation, does the problem go away?
It sounds like you can connect to one database, but not the one you need. Is that correct?
The ASPNET user is a Windows XP thing. You should generally use NETWORK SERVICE for server-based deployments.
So, you can connect from Management Studio, but not from IIS? What identity are you using for the IIS AppPool?
Can you connect if you use Cassini (the web server that comes with Visual Studio)? That should pass through your user ID.