How Can I Verify The Availability Of An SQL Server
Nov 18, 2006
Hello everyone,
I have an ASP application mainly connected to one SQL database that works great but now I am trying to add some functionality that requires to connect to another remote SQL server. Till now all is fine except that the remote SQL server is not always online and of course when this happens my ASP application stops with the following error:
Error Type:
Microsoft OLE DB Provider for SQL Server (0x80004005)
[DBNETLIB][ConnectionOpen (Connect()).]Specified SQL server not found.
in my Global.asa I setup my session variables for DSN connections and in my pages I call my SQL connection as follow:
Set Conn = Server.CreateObject("ADODB.Connection")
Conn.Open Session("MySQL")
SQL = "my SQL statement here;"
Set RS = Conn.Execute(SQL)
Every time the page hits the Conn.Open line I get the error if the remote SQL is not online!!!
Is there a way I can check a sort of returned error code holding the connection status before getting to the Conn.Open line???
For example: SQL Server is installed on a machine and you want to verify its setup to make sure everything is intact, what are the key things you go and look out for?
I posted this to the ms sql clustering news group, but I thought I'dpost it here just in case someone here knew the answser. This problemhas had me baffled for 5 months, and I'm not seeing any supportarticles from Microsoft on it, yet. Anyone here got a clue?About 5 months ago, I posted a query to this group after experiencingfailures with my database maintenance plans (during the verify phase)that run on SQL Clusters on Windows 2003(http://groups-beta.google.com/group...9b?dmode=source)I was re-posting this in hopes that someone knows of a fix besidescoding a home-brew verify step in to the backup job to check the file'sintegrity?Thanks,TW
I inherited some SQL 2005 server boxes with NO CDs to be found...Is there any easy way to verfiy if these SQL boxes were trial edtions or full licensed production version...?
Trying to upgrade a 6.5 to a 2K. Running SQL Agent from an admin account, admin account active as admin on both 6.5 machine and 2K machine, but I can not get the upgrade past the second screen, where I get the error message: Unable to connect to export server, please verify that you are an NT Administrator on that machine.
need to migrate a cluster with an AG dtabases to new data center cluster with AG.
I was wondering if is possible to do mirroring on top of the AG configuration? or what other options could be to migrate a cluster that has 3 nodes and setup the ag databases to a new datacenter.
Once complete, "select SERVERPROPERTY('LicenseType')" returns DISABLED, but I expected that it would return PER_SEAT.
Thankfully, after the upgrade it does show EDITION=Standard Edition.
Questions:
1. How do I verify the license installed is the Client Access License of 5?
-- SQL Server 2005 does not seem to have the same SQL Licence control panel as did SQL 2000. It is not listed under Control Panel -> Licensing (only thing listed is 'Windows Server') nor under Administrator Tools -> Licensing.
2. How do you add CALs or change license type in SQL 2005?
-- I was also puzzled that I was not asked during setup of the license mode and/or number of licenses ( I did not get this on a fresh install of SQL 2005 SE either ).
I got through the installation hoops for SQLEXPRESS Reporting Services in Vista and set up the default configurations in Report Services Configuration. I can explore the default directory for "Reports" in IIS7, but I can't browse in IE. I get the "The report server is not responding. verify that the report server..." message in the browser. This is after I migrated the app per the initial http 500 error using the preferred method - %systemroot%system32inetservAPPCMD.exe migrate config "Default Web Site/Reports".
I'm running Vista Ultimate, VS2005, SQLEXPRESS SP2. I've tried running IE as admin and also I've disabled UAC from gpedit.msc - ...Windows SettingsSecurity SettingsLocal PolicySecurity Options and unchecking UAC.
I am in the process of setting up server replication using the Central Publisher Model. We are doing this for application availability. The application is a .NET app and this application uses the SQL Server name in the connection string. As far as I know we can€™t have two severs on the same domain with the same name. So if our primary server (server A) goes down and that server name is in the connection string how does the application get redirected to our backup server (server B). Thanks for the help.
When I trying to configure Reposrting services in IIS & XP. It hsows me error "The report server is not responding. Verify that the report server is running and can be accessed from this computer."
I also configure with reposrting configuration tools which show all confuguration is perfect.
but when I try to open through IE http://localhost/Reports/Pages/Folder.aspx
or http://localhost/Reportserver
It shows error. I try all ways still not works ..Help me out
I want two write a small script to determine which is the currently active (primary) server in the AG.
Right now, I see that using SELECT * FROM SYS.dm_hadr_availability_replica_states I can determine the role. However, when the server goes down and switches to the secondary node, I don't believe that the role changes (or does it?). How do I determine which is the active node?
I've been asked to look into the possibility of using SQL Server in a high availability environment. We have a few web based applications that use SQL Server back end DBs. What we are looking into is whether we can use multiple instances (on multiple physical servers) of SQL Server using some type of clustering/load balancing. I haven't worked with SQL Replication before, so I'm not even sure where to start in exploring the possible avenues we can explore.
Can anyone push me in the right direction? Any info would be greatly appreciated!
I am building an SSIS package that is hitting about 50 remote servers. I have a for each loop container that i am using to build the list of servers to run.
The problem is...sometimes networks go down, sometimes connections time out and this causes my entire package to fail. I inserted a task that will run select @@ServerName on the remote server inside the loop. My thought was, if this returns an error I could ignore it and move on to the next server in the list and log somewhere that server x threw an error. Logging is easy, the problem is, how do I then tell it to move on to the next server in the loop?
If anyone has any suggestions on how better to do this, I am open for alternatives...
PROD1(cluster 1) Clustered SQL instance1 PROD2(cluster 1) DR 1 (cluster 2) Clustered SQL insatace 2 DR 2 (cluster 2)
I have set an availability group up from the PROD instance to the DR instance.How does the AG behave if a SQL instance fails at PROD? Does it try to fail over to Node 2 on Prod before going over to DR? or bring the Replica at DR online straight away? Can we only use Manual Failover of the AG in this scenario to make use of the High Availability of the Windows cluster?
The MSDN doc makes it sound like after a failover of the primary, the CDC data won't "keep working" on the secondary unless you "To allow the logreader to proceed further and still have disaster recovery capacity, remove the original primary replica from the availability group using ALTER AVAILABITY GROUP <group_name> REMOVE REPLICA. Then add a new secondary replica to the availability group."
We have a few CDC tracked tables that we use and the general idea of AlwaysOn I thought was to minimize all the overhead and let things "just work" so your apps just connect and the listener re-routes everything where it needs to go.
It looks like to get this working properly an automated job /trigger would have to wait for a failover event and then kick off tasks to remove and re-add the replica and perhaps start up the CDC job on the secondary?
I am trying to create a job that runs against my High Availability listener server.
It is a fairly simple SQL statement in the job - execute tsql.
When I try and run the job I get the error:
Executed as user: NT SERVICESQLAgent$SQL2014A. The target database ('BB_Prod') is in an availability group and is currently accessible for connections when the application intent is set to read only. For more information about application intent, see SQL Server Books Online. [SQLSTATE 42000] (Error 978). The step failed.
I thought there was a way to run a select statement as a job against the listener? The tsql step is only a select.
Is there a way to pass in the application intent = readonly as part of my SQL statement?
I have Configured always on Availability groups between Server 1 Primary Replica(Active), server 2 Secondary Replica(Passive) on top of WCFS...
Listener Name: AGListner( CLIENTS/APPLICATIONS connect using this Name)
Testing Scenario 1(on Virtual Servers):
I have turned network down on Server 1(primary) , then secondary server (Passive ) one came ONLINE and this is now the primary and i was able to connect to AGListner.now When i try to SHUTDOWN/POWER OFF PRIMARY(current Active server),failover happened to Secondary successfully but lost cluster and lost AGListner and was not able to connect ....now applications which are trying to connect using AGListenr name will loose all connections..does AlwaysOn Availability does not support Server SHUTDOWN/POWER OFF?or is there a way to resolve this? or am i doing wrong somewhere?
automatically replicates new databases to Availability Group partners - if you do a little prep work on your environment first.To make it work:
1) Create linked servers on all group members pointing to all other servers in the group, with names matching the hostnames they represent. 2) Ensure suitable credentials (or 'current context' impersonation) for linked servers. Also: Enable RPC and RPC OUT 3) Run the DDL code below. 4) Schedule hadr_replicate_queue on [master] to run as often as you want initial syncs to occur. Every 5-10 minutes is plenty for most purposes. 5) Connect to an availability group listener and call CREATE DATABASE :)
I use a slightly more extended version of this code at home to do things like permissions synchronization across replicas - I essentially allow applications to install direct to an availability group replica and then have all the relevant objects replicate to other nodes. I don't really like going through manually and doing things, even though there's an AddIn from SQLSkills for management studio - it still requires manual intervention.
The main use I have for this at home is that I'm using the Azure pack, and want to automatically ensure that my newly created 'SQL Server Cloud' databases are highly available, plus it means when I install a non-alwayson aware product it doesn't require any extra work afterwards to allow failover to another machine.
* AlwaysOn Self-Population Script * By: Steve Gray / steve@mostlyharmful.net * Usage: Free, but buy me a beer if you're ever in Brisbane. **/ USE [master] GO IF EXISTS (SELECT * FROM sys.tables WHERE name='hadr_pending_replicate')
We are having a conversation at work and the subject of load balancing with SQL came up. Right now we are running SQL Server 2014 on four (4) machines. I am using a AlwaysOn with Availability Groups (AG). Now I know that we can scale out the reading in AG by allowing the secondary serves to receive reads.
Is there a way to be able to do this with writes? Can I have in essences 2 masters that some how reconcile with each other? We are expecting a huge amount of writes in the near future and we need a way for SQL to handle the amount of traffic we are expecting with out any issues.
I explored the possibility of Peer - to - Peer replication; however, it seems that it would be more work if we are constantly making updates to the database scheme.
