I have an OLTP server that I am thinking of setting up transactional replication for in order to support OLAP Reporting.
I have a server named Yoda that we are using for our OLTP and one named Chewie for our OLAP server (Both are VM servers). I know I can setup transaction replication on them easily. However, in thinking of network IO and performance and talking it over with the network admin we were thinking of adding a 2nd nick card to both servers and running the replication commands across there.
So they would have something similar to below:
Yoda: 192.168.XX.51:1433 (Main OLTP Transactions)
192.168.XX.52:874 (Replication Transactions)
Chewie: 192.168.XX.21:1433 (Usual SQL Agent Transaction)
192.168.XX.22:874 (Replication Transaction)
In Microsoft forums I was told that this could be done using Routes. However, I am new to routes in SQL Server so I am not sure where to begin. How would I create one that I can tie to Transaction Replication?
A Windows server may have multiple IP addresses, either on one or across multiple NICs.
After a second IP has been assigned to the host, configure SQL Server to listen to that IP/port using SQL Server Network Configuration.
Here you may modify the port to listen to, but probably unnecessary to use different ports when using multiple IPs. Each IP can be listening to port 1433.
You may create additional CNAMES or aliases to reach the database instance with different host names.
Creating a Valid Connection String Using TCP/IP
SQL Server also support aliases.
Related
What is the difference between Connection, instances, and sessions in the SQL server? I tried to find the differences but one and others are interrelated.
Connection: It is the number of instances connected to the database.
Sessions: A session run queries.
Instance: It is a copy of the sqlservr.exe executable that runs as an operating system.
Any explanation with examples would be helpful.
A connection refers to the layer-4 (TCP or Named Pipes or Shared Memory or etc...) connection between a client and the server.
A session is the "logical" unit of a client connection and uniquely identifies a client. A session can have multiple active commands and is the entity which "holds" locks on an object. Sessions are normally 1:1 with connections (the exception that comes to mind is the Context Connection.)
An instance is the SQL Server process running on a server which provides the SQL Interface to the databases. It frequently listens on TCP ports to accept connections from clients to create new sessions.
I need to discover the running db2 servers in a network.
I tried to connect to all servers in the network using the JDBC connection. But the problem is while using JDBC, we need to specify the database name in the URL. As of now, I tried to connect to the SAMPLE database. But if a db2 instance does not have the SAMPLE database, the connection will fail.
So I want to know the other possibilities to discover db2 servers in a network and also Is there any way to connect to the instance of the db2 server unlike connecting to a particular database(Similar to SQL - Connecting to an instance using port only)
Db2 administration server (DAS) has the corresponding functionality. Refer to the following link:
Discovery of administration servers, instances, and databases.
Note, that DAS is deprecated and may be removed in future Db2 releases.
I have a SQL Server on a VLAN that I have read permissions to and I need a SQL Server instance on an external network to be synced. I only have read permissions and our partner won't allow us to configure replication so that's not an option. On top of all that because it's on a vlan the external SQL Server can't connect to it directly.
I think my best bet now is simply to write an application (most likely in C#) that will detect changes and push them to the external SQL Server. This approach doesn't seem ideal.
Are there any out of the box ways to do this or any tried and true methods?
PI'm trying to do replicate two data bases.
DB in LAN network (Publisher)
DB in virtual dedicated network (Subscriber)
According to my situation, replicate publisher implemented in my server in LAN network.But subscriber is implementing on a virtual dedicated server. i configured router port to my server machine in LAN network.using sql management studio on virtual server, i connected to the db in LAN network.But when i try to create subscriber using virtual server db i can't access to the publisher.(IN LAN network.) it gives errors as below.
"SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, 'BESTLIFE\BESTLIFECROWN'. (Replication.Utilities)"
Please help me to solve this .
You didn't say whether you used the GUI or scripts, but somewhere, a call got made to one of the stored procedures (likely sp_addsubscription) with a server name that doesn't match the actual server name. For instance, the error message above says that the server is called BESTLIFE\BESTLIFECROWN. If that's not the name of the server that you put in as hosting the subscriber, it's not going to work. Whether you need to add a DNS alias or whatever, that's the only value that will work for this setup.
I am working on a database application that runs on various independent servers.
Each server runs an Instance of SQL Server 2005 with the same database. We would have a Master Server where that would be the definitive source of information and various "Client" Servers that would be distributed around (with no network connection of any kind). This Client Servers would return from time to time (lets say once a week) to be synchronized with the Master. Simply put the process would be.
1) Update the database on the master server with all the modifications from a client server (taking into account not overwriting changes made by the update process of a different client server [that would update the same master server])
2) Copy an updated version of the master server database to the client server.
Thanks for any help
MS SQL Integration Services may help:
http://www.microsoft.com/sql/technologies/integration/default.mspx
Also check for database replication. Check the Master-Remote part too.