Hello, Heros of The Programming World!
How it is possible to perform "replication" between two databases using technological means of MS SQL Server 2005 if two servers do not have a connection at all. The only thing is possible - is transfer of data for the replication on a CD.
What is the best way to do it if central database has a hundreds of such "subscribers"?
We recently installed another SQL Server so we could test performance of replication between
the two servers. After I set up the replication between the two I got the following error:
subscriber must be running in Per Seat (Named User) licensing mode to use this replication feature.
Is there any way around this? Or could you direct me to some documention pertaining to
this error?
Thank you
Hi:
We have a project that will consist of 3 production servers in 3 different
regions and each server has it`s own clients in that region. We want to use
replication to keep them all in synch so that if one goes down, the client
PC`s would just re-connect to one of the other two remaining servers and
keep working.
1. I am wondering what type of replication to use?
2. I was leaning towards merge, but was wondering how to use it to keep 3
servers in synch? If I use the Central publisher with updating subscribers
scenario, I foresee a potential problem as follows:
A. Server1 is central publisher
B. Server2 and Server3 are updating subscribers
C. Server2 (or Server3) goes down, clients reconnect to Server1 and
keep working.
D. When Server2 (or Server3) is back up, Server1 will push all
changes back to Server2.
but,
E. Server1 goes down, clients reconnect to either Server2 or
Server3 and keep working.
F. Since Server1 is down, changes made to Server2 not replicated
back to Server3 (The central publisher is gone) until Server1 comes back up.
G. Server2 goes down while Server1 is down, clients re-connect to
Server3.
H. The changes made to Server2 were not replicated to Server3
because the central publisher is missing.
I. Server3 therefore is missing data changes.
Please help me figure this out. I feel as if I am missing something that I
could do to also keep Server2 and Server3 in synch with each other besides
the Central Publisher.
Thanks in advance!
Jay Natarajan
suppose i am repliacting(Transactional Replication) to two servers using the same publications can i stop replicating to one server without disturbing the other server?
If i resume the replication to the server after two days what will happen to the two day's data?will they be replicated when i resume the replication?
Thank you
Can some one please give me a quick,brief description on the "Major diffrences" between these to features? Thank You, JJ
View 1 Replies View RelatedServer_1 contains DB_A and DB_B. Server_2 contains DB_A and DB_B.
Can replication be setup where Server_1 DB_A (publisher) publishes to Server_2
DB_A (subscriber) and Server_2 DB_B (publisher) publishes to Server_1 DB_B (subscriber)? The environment is NT 4 (sp3) and SQL 6.5 (sp5a). Thanks in advance.
Hi
I have two SQL Servers (6.5). One based in London (LDNINNTS9) and one in New York (NYINNTS2).
I had bidirectional replication set up on one table in a DB and everything is (WAS!!!) working fine. Came to work this morning (Monday typical!) and the following has happened.
When I select the remote servers option on the NY server from Enterprise manager I get the following error message
Unable to connect to site '0'because '' is not defined as a remote server.
Now it says that '' is not defined as a remote server. So I did a select of @@Servername and it has returned (null). It was set to NYINNTS2. I have tried executing some ISQL to change the name and started and stopped the SQL Services but the name remains (null). Does anyone have an idea of what I can do to set the name up as it was?
I know that the Server name gets set to null if it is invalid, but I am trying to set it to NYINNTS2, which should not be invalid? Does the domain name impact the validity of the name?
HELP!!!!
Regards
Steve Farmer
Hi All,
Just want to know if we can replicate data (Transactional Replication) from a clustered servers (server A and Server B are active-passive clustered running SqlServer 7) to another server C running SqlServer 7.
If yes, how to go about doing this. Any white papers, KB articles or books out there which will walk through the steps to do it.
Appriciate any help.
Thanks,
Sri
Anyone know what or how to calculate how much bandwidth I may use during replication. I have done this with large pipes with out a problem, just concerned I may need to change the interval to something else.
Thanks
JJ
Hi There Gurus - Another Replication question for you all:
Can anyone point me in the right direction to get info on using Linked Servers in Snapshot Replication?
We have Replication all scripted & working between Registered servers, but one of our divisions is not allowing us to register their box on the Parent - ONLY a Linked server.
Thanks in Advance Everyone...
RobbieD
Hi! need your help.
I have 2 dedicated sql servers xx.xx.x.155 and xx.xx.x.165 (Hosted Environment)
Both SQL Server 2005.
I need to replicate (snapshot daily) data from 155 (Apollo1) to 165 (Apollo2).
and I have many questions as this is the 1st time that I work on this environment.
I created 3 windows accounts and was able to create the publications (Apollo1).
Apollo1ReplSnapAgent
Apollo1ReplDistAgent
Apollo1PublisherUser
However (the distributor) is not visible to Apollo2 so I am unable to subscribe.
Do you have any idea what I need to do to make it visible?
I setup an ftp site to drop the publication (as I was unable to create an UNC Share) and I was hoping to be able to subscribe to it.
Probably it is a matter of permissions...maybe a firewall? should I ask my provider to open a port? do I need to create the same 3 accounts in the Subscriber?
something like Apollo2SubscriberUser?
Please help!
I am lost!
Hi,
I have 2 DB as X and Y.
They are on 2 Servers A and B.
I am in need to create a stored procedure by getting a value from table1 in DB X on Server A and then use that value to get info from table2 in DB Y on Server B.
I am looking for a connection string to let me connect to DB X on Server A and DB Y on Server B.
Can anyone help!!!
Thanks.
Hi,
I tried with success to replicate a table_test_repl from my local server to an other server.
I used only one table for testing.
After that, i can't drop the 2 tables a_test_repl (on my local server and the other : I've got a message 'cannot drop the table because it is published for replication'
What can I do? I need absolutely to drop these tables to keep a clean model
and I can't drop the database and try again.
Thanks to your answers
Axel
Hello,Being a bit of a SQL Server novice, need some advice with the followingsituation.Server A and Server B have SQLServer 2000 based databases. The vendorof the application/system has implemented their own replication processto ensure the 2 databases are in sync. However, there is no clusteringwith virtual IP addresses implemented. So to an external client/db, itis 2 identical databases with the same name on 2 distinct servers.We need to develop an application that will reside on a networkedserver C and with SQLServer 2000 as well. While most of the tables inthis database are self contained, around 10 tables will have to bemirror copies of the same tables from either Server A or Server B.Question, how do we implement subscription based replication on top ofa redundant database, when no clustering is implemented? So, inessence, when Server A is alive, the database on Server C willperiodically (or on change) replicate the 10 tables from Server A. WhenServer A is not alive, it needs to do same from server B. (When bothserver A and B are alive, it is acceptable to get data from either,since they are synchronized internally).Any alternate suggestions on achieving this functionality are welcometoo. If SQL Server 2005 has some capabilities that may address thisproblem, that is a consideration as well.Thanks
View 1 Replies View RelatedI am having trouble finding any documentation on how linked servers are set-up under SQL 2005 for log-shipping and replication. Under SQL 2000, the only linked servers "visible" were ones that were user-defined. Under SQL 2005, it seems when you set-up log-shipping or replication, you get these new linked servers which are automatically defined. I would like to understand them and in particular, how security is maintained. We recently had a production issue where after some problem with a server which resulted in having to restart SQL Server, and shrink msdb, log-shipping started to fail authentication when trying to run alert jobs. Only after rebooting the server, and also the log-ship target server, and waiting 9 hours, did the authentication correct itself. I would like to know how it resolved itself and what took so long?
View 3 Replies View RelatedThe setup: Two sql server 2005 SP1 clusters replicating with about 25 transactional publications and 10 merge publications. (Both clusters are being tested, nothing is in publication)
Currently, the servers are in the same building, which is prone to power outages. When a power outage occurs, how are the publications going to act once power is restored? Will we have to reinitialize the publications? This would be bad considering one of our publications takes around four hours to deliver a complete snapshot. What happens if one of the clusters where to go offline? When it comes back would it continue to replicate, or would the publication need to be reinitialized? Curious if anyone has any experience with this.
I've tried searching for any articles on this topic and have not been successful. If anyone knows of any, point me in that direction. Thanks!
-mike
Hi
Windows XP Pro, SQL Server 2005 (Developer) & Visual Studio 2005 (Pro)
New SSIS project (Visual Studio)
New OLE DB/SQL Native client connection.
There's no servers available in the drop down box.
All the services that need to be running are running.
Guess I've missed the obvious here
Cheers
Dave
Hi guys, right now I am facing this scenario several times and I wonder why it can be happen. Both SQL servers are in Enterprise SP1 edition. The mirroring setup can be work fine to me. Once my principal get attacking by DDOS, then mirroring session change the status to 'DISCONNECTED'. However, after DDOS attack solved and line connection gets back on the principal server, the mirroring session still remain to the status ('DISCONNECTED'). If I restart the SQL services on principal server or mirror server, then only the mirroring session change to 'SYNCHRONIZING' status. Does anyone faced this happen before? I need some assistance on it and hope able to get any explanation or solution from you guys. Thanx and have a nice day.
Best Regards,
Hans
Hi, guys.A very simple question for all of you: how can I get the amount ofbytes exchanged during a Merge replication between two Microsoft SQL2000 servers?Thank you.Bye,Angelo.-
View 1 Replies View RelatedHello,
We have an environment with 7 servers that are running replication with one another and I'm wondering if there are any tools or experiences that any of you might have that may assist in the auditing of these servers. The data should be in synch accross the boards for all tables, but sometimes problems can arise such as replication not being set up properly, stored procedure's being out of synch, or data gliches etc.
In dealing with these issues we have an in-house written program which analises each table on each server and takes a snapshot and does column by column compare. We also have another program that will synch the data up (basically a delete/insert statement on the publisher). This process can take up to 3 weeks for our quarterly update of every table. I'm wondering if anybody has used any tools such as in SSIS or a third party tool and has done or is doing something similar to what we are doing now. If so, are there any tips you wouldn't mind sharing on how our process might be sped up?
Thanks,
Phil
When setting up an ODBC connection on a non-sql Server X and choosing from the drop down menu which SQL Server to connect to, I see two identical names for my SQL Server (Y). No matter which one I choose, Im not able to go to the screen after being asked how I want to log in (SQL server authentication)
If I build a ODBC connection from any other desktop, I only see one SQL Server Y, and am able to establish a connection to SQL Server Y, with the same user account and password as when Im on Server X.
Server X has two network cards and is teamed...could that be a possible problem ?
Any ideas ?...Thank you
Being an IT consultant, I have to visit a number of customers having applications running on SQL Servers that implement trusted connection security model. In addition, all of these companies have their own DOMAIN settings, and security implementation.
How can I access to databases without changing the DOMAIN settings of MY notebook? I do not want them to switch to SQL security model, and I do not want to create any security hole in those companies.
What shall I want from the system administrator so that I can login into their domain without changing my domain settings?
Thanks,
EIO.
Hi,
We currently have a test and development environment for our data warehouse which is using SSIS packages to build (SSIS packages call stored procedures). We have multiple connections accross the different packages. The problem that we are having is when we deploy the packages to the development environment, the connection strings in the packages are still pointing to the live server! Hence, when we run these packages in the test environment, they actually execute the stored procedures in our live server.
I have tried to use package configurations and the deployment utility to assist us in this regard but have still come up with a few problems:
- When running the deployment utility, I still have to go and manually type in the data source the connection string must use - Is there maybe a way to use some sort of a variable that will automatically set this dependant on the name of the server that you are deploying to?
-It seems, even when I deploy to my live server, if I change the data source to point to my live server, it goes and changes the data source for the packages on my test server to point to the live servesr as well/
Basically, what I would like at the end of the day is to just be able to select the server the packages must be deployed to, and the connesction strings must be set automatically to either the test or live server dependong on which one I deploy to. Anyone know if this is possible?
Thanks in advance
I have multiple web databases for storefront orders as linked servers on SQL Server 2008 R2. I need to organize the data for these orders into a structure that can be imported into my ERP application db frequently either on demand or periodically during the day. We are essentially trying to make the manual order entry process automated. My thought was to get the data into views that resemble the schema of the order table in my application db and then schedule a stored procedure with sql jobs or a load routine from within the ERP application that would insert data from the view into the order table.
View 2 Replies View RelatedWhat is the best way to run SSIS scripts on different servers without changing connection information. Our test server is ppntt140 and our production server is ppntd110. If I create a script on server ppntt140 what can I do so I can move it to server ppntd110 without changing any connection information? Database names are the same, it is just the server that changes. What is the best way to handle this? Thanks in advance.
View 4 Replies View RelatedI was wondering if someone could help explaining how the SQL Server handles all incoming connections, I and a friend started a discussion about using the connection pool in ADO.NET or not in a specific case.
Usually when creating like an ASP.NET Page it's recommended to use the connection pool, because it optimizes the performance, by using already created connection, so we don't have to recreate the connection all the time. I have always thought that the connection in the connection pool had an open connection on the server. So 5 connections in the connection pool, would be 5 open connections at the server. But after having the discussion with my friend I am not so sure anymore.
Say that I would create a client application (.NET using ADO.NET) that connects to the database and work with that data. If I then have 1.000 clients and each client have a connection pool with 5 connections in it (I think that the default numbers for the connection pool), then there would be like 5.000 open connections on the SQL Server, where most of the connections actually never do anything more than hanging around and waiting... And then the connectionpool is not 1 per client but 1 per connectionstring.
So if my client scenario would access data from 2 different databases, there would actually be 10.000 open connections at the SQL Server. So now I think that there must be a server connection pool or something to handle the connection from the clients. So that there would only be like 10-50 open connections at the server for the 1.000 Clients that was connected.
How is it? Is there 1 open connection in the server for every connection in the connection pool? If that's the case, it would be better for the SQL Server if I don't not use the connection pool in the client, but instead open the connection when we need it, and then close it, and taking that little performance hit every time, to help the performance on the SQL Server.
Best regards
- Magnus
I am having MSSQLServer2000 on Win2k and Win2k3 server.
i have to connect these servers from a application using JDBC driver and AD Authentication.
I have programmed all the things needed for AD authentication in my application(changed url , using integratedSecurity=true), and it is working fine when my application connects to MSSQLServer2k5 on WinXP(which is added to same domain of my application).
But when i try to connect MSSQL2000 server on Win2000 server it failes and gives error as follows.
Apr 18, 2008 12:39:51 PM com.microsoft.sqlserver.jdbc.AuthenticationJNI SNISecGenClientContextINFO: Failed to get the SPNcom.microsoft.sqlserver.jdbc.SQLServerException: Connection reset at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSChannel.read(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSReader.readResponse(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at ChangePassword.process(ChangePassword.java:33) at ChangePassword.main(ChangePassword.java:14)
I am using following code for connection --
String url = "jdbcqlserver://172.16.1.243\dbaudit;portNumber=1034;integratedSecurity=true";
Class dbDriverClass = Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
Driver driver = (Driver) dbDriverClass.newInstance();
Properties props = new Properties();
conn=driver.connect(url, props);
All;
After we change servername of the publisher server, I got the error
'Could not connect to Subscriber...'
Please help.
Thanks
Fuan Zhao
Hi,..Please help me..
We have two server on pulbilc ip A , B in other country, and there replication will working fine. But i want to replicate data from one online server(A) to my local office(in my country) server(C). means from public ip to private(A->C). then some one told me that you have to put both server on public for replication. after the i put my local server(c) on public ip. but now i am facing the problem that i am able to connect C to A(means my office server to other country server) but not able to connect A to C(means other country server to my office server). when i am connecting from A to C then error shows is "defaut sqlserver server does not allow remote connection". I have change all the sql settings..and also done required changes in firewall but not successed. my operating system 2003 and database sql2005........ please help me................ASAP
thanks and regards
Vipin yadav
Hello, I only need to know if I need to have a bidirectionnal connection between the subscriber and the publisher for merge replication or if the connection ca be openned only from the publisher to the subscriber if i use the push subscription option.
Thanks in advance
Hi
I have a problem when trying to setup replication between two SQL servers on different networks.
My publication server is SQL Server 2005 Standard Edition. My subscription server is SQL server 2005 Express Edition
I have setup the publication no problem but am now trying to create my subscriber. However, when trying to connect to the server, I receive the following error:
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, 'W2M-RDC-01'. (Microsoft.SqlServer.
However, because the servers are not on the same network, I cannot use the server name.
Why does it not allow you to connect to an IP?
Is there a way to create an alias? I have read that you can but am unsure how to do this. Do I need to change the hosts file? If so, where can I find this and what exactly do I need to change?
Kind Regards
Dan Rostron
I have a report that was designed using SQL Reporting Services that sits on a SQL reporting server. It's nothing too exciting, it is essentially a three page application with legal jumbo on pages 2 and 3 and applicant data in fields on page 1.
We use rectangles to force page breaks to page 2 and to page 3.
When running the report on the report server, it shows and prints fine.
When running the report from the QA website internally, it shows and prints just fine.
When running the report from the production website from a machine internally, it shows and prints just fine.
When running the report from outside of the company network, the report is jacked. It obliterates large chunks of text, crams text together, and creates blank pages.
I need help in determining where I even begin with trouble shooting this!
Hello,
I've been looking around in several SQL-Forums and in SQL Books Online but haven't found clear suggestions how to tackle my problem:
Our company has to fill a database with documentation for our contractor. Our subcontractors have to supply information from their branch/craft into this database, too.
Replication (without determining a type at this time) would do fine for data-exchange between us and our subcontractors.
But for working in different companies the networks are not connected
and in some companies/departments connection to the Internet is prohibited at all.
This would result in data-exchange based on files - which wont be a problem as data needs to be updated/exchanged only once a week and is usually done at meetings using DVD-Rs.
scenario in short:
- two-way exchange of data between SQL servers being not connected
- update needed once a week
- our server: SQL Server 2005 Standard (preferred)
- servers of our subcontractors: SQL Server Express 2005 (preferred)
That's the point where I dont know how to proceed:
Is two-way replication based on files possible at all?
I read about Snapshots, but to my understanding this replaces the "whole database" without caring about changes made to it and that's why it wont work for two-way exchange.
I would appreciate your hints how to solve this problem in general or whether I should look out for other solutions - MS Access might work with restrictions - but I would prefer SQL Server.
Thanks for reading until here and in advance for your answers.
Regards,
Michael__H