Hi,I'm trying to setup replication using SQL 2000 as the publisher and SQL 2005 as the subscriber.The problem I have is that the SQL 2000 instance is running on a non standard port 1083, so the name of the instance I'm connecting to is: TESTPC1SQL2000,1083SQL 2005 requires you to provide the "requires the actual server name" which would be "TESTPC1SQL2000" which unfortunately will not work as it's on a different port.The error message I'm getting when attempting to setup the subscription on SQL 2005 Management Studio is this:TITLE: Connect to Server------------------------------Cannot connect to TESTPC1SQL2000,1083.------------------------------ADDITIONAL INFORMATION: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, 'TESTPC1SQL2000'. (Replication.Utilities)Does anyone know a workaround to this?Thanks,Andy
I'm trying to set up a transactional replication from SQl Server 2005 to SQl server 2000. The Distributor and the publisher are on our server and the subscription is supposed to be on a SQL 2000 server on a different location. Before upgrading to 2005 I didn't have problems - the replication from 2000 to 2000 was working perfectly.
After I succesfully created the distributor and the publication the first problem that I encountered was that when I tried to create the subscription it was giving me an error that I cannot use an IP to acces the server. I realized to fix that issue by creating an Alias in the SQL Server Configuration Manager for the server where I wanted to create the subscription (a push subscription).
Now when I try to add the subscriber it gives me another message "Execute permission denied on object 'sp_MS_replication_installed', database 'master', owner 'dbo'" - so I cannot create the subscriber.
The user that I use to create the subscriber on the 2000 server is dbo for the subscriber database but it doesn't have rights on the master database. Also I realized that on the 2000 server I still have the old subscription but I cannot delete it - for the same reason - no access on the master database. Before upgrading to 2005 I had the exact same rights on the 2000 server.
I have transactional replication setup from server A to Server B. I wanted to move the subscriber from B to C. What could be the best approach.
1. Backup the DB from Server B and restore on Server C. set the replication between A & C. 2. setup the transaction replication between A & C along between A & B. Test A& C working fine and then remove B.
If I am going with approach 2 , I have to replicate data approx. 70 GB so If I ran both the replication on Server A that will stress as 140 GB of data moving out. How do I control this large movement ? Can the replication be manual synch?
I know that SQL Server Express 2005 can subscribet to SQL Server 2000 publications. However, it seems that SQL server 2000 cannot perform a push to SQL Express.
Can anyone refer me to any online help or documentation on how a proper replication can be done between SQL 2005 Exress and SQL 2000??
Hi Nerds There are 2 production servers (SQL Server 6.5). One is publisher and the other one is subscriber. Data is replicated from publisher to subscriber which is a transaction based replication. Each day at 8:00PM data comes into publisher and the updations,replication,backup,reporting are carried out till 11:00AM next day. The subscriber server is used as a reporting server and the publishing server is used as the data warehouse server. I want to cleanup a table on the publisher. Since it is replicated on the subscriber, can I do delete operation on the subscriber, make the subscriber server a publisher and the publisher server a subscriber, do replication from publisher(new) to subscriber(new) and again change publisher to subscriber and subscriber to publisher without affecting the production line of the databases. I have to do this between 11:00AM to 8:00PM. Pranav.
I am getting "Row not found on subscriber" error on the subscriber. I am trying to find the root cause.
1. Records get lost during publication initialization from backup, could not reproduce it though. I was inserting records in a loop into a replicated table while initializing the publication from backup. After the backup/restore finished, I have stopped the insert, allowed the replication to catch up and compared the row count, it was identical.
2. Someone or some process is deleting the records on the subscriber. Setup Audit, but could not confirm this theory so far.
3. Records get deleted twice, as we publish the execution of some bulk delete archive jobs, to fix latency issues. Found this article, which says, this is not the case:
[URL]
4. Records are deleted on the subscriber by triggers. The impacted database has no triggers.
i have replication setup and working, there are 3 subscribers and now i want to add a 4th one. is it ok if i just add the subscriber and reinitialize replication?
I just upgraded my SQL 2000 server to SQL2005. I forked out all that money, and now it takes 4~5 seconds for a webpage to load. You can see for yourself. It's pathetic. When I ran SQL2000, i was getting instant results on any webpage. I can't find any tool to optimize the tables or databases. And when I used caused SQL Server to use 100% cpu and 500+MB of ram. I can't have this.Can anyone give me some tips as to why SQL 2005 is so slow?
We have a central office with a SQL2005SP4 server (yeah, I know... old as heck) that's the main database and it has multiple subscribers in regional offices. Well... one of the regional offices server is failing, and it needs to be replace.
The original server is an ancient Win2003 86x
The Server team will build a new Win2008r2 64x, and use the same name and IP address
And I'm tasked with the SQL part.
I'll be installing the same version/patch of SQL, but 64x instead, and migrate all databases, including the system databases.
How do I handle replication? Do I need to reintialize from scratch? or can I just use the backup as a starting point?
Any experience of success or failure setting up CDC on the subscriber end of transactional replication?
Also for a bonus answer, why are explicit index operations not permitted (I'm assuming this is even on the publisher?) From BOL:
• Explicitly adding, dropping, or altering indexes is not supported. Indexes created implicitly for constraints (such as a primary key constraint) are supported.
When creating the snapshot I didn't choose the option copy non-clustered indexes. I created some indexes manually on subscriber database. Replication failed later with some issue.
so reinitialized with new snapshot but all the indexes are gone from the subscriber database.
How to keep the indexes without dropping from subscriber database whenever we reinitialized with snapshot
I have been adding a lot of Articles for Publication.
They make it to the distributer but they do not make it to the subscriber.
If I add articles before the previous batch of articles get applied to the subscriber could that cause a problem and for replication to become out of sync?
It is a pull transactional replication.
I have had to generate a snapshot for the problem to go away but it keeps happening.
I have Two databases,that same schemas and same tables. that both servers are different location. but data must be update and input from both sites.that data must be same both.
so i've planed to replication data both servers,then i must chose merge replication right?
so i'm set
server1 (assumed server1 as main) are Distributor/Publisher
and
server2 just Subscriber only
that i can configuration successfully.
then i'm chose push replication from server1 but it's not work.
this is error message that show
The process could not deliver the snapshot to the Subscriber.
please advise me what's wrong and how to fix problem?
I have a setup of transaction replication between one publisher and subscriber in the Same server.Now, I need to add a new subscriber to the existing publisher. So publisher database name is DB_A and Subscriber 1 name is DB_B. So the new subscriber will be DB_C. Is this kind of setup possible on one server?
If yes then at the time of reinitialization is it going to apply the snapshot on DB_B as well as DB_C?Also let say if due to disk error DB_B gets corrupted then will data be still replicated between DB_A and DB_C? (Assuming publisher, subscriber 1 and 2 are sitting on individual disks).
I am getting the error The transaction log for database 'ReplicationDB' is full due to 'LOG_BACKUP'.log_reuse_wait_desc from sys.databases is showing logbackup
The database is subscribed database. We configured transactional replication. But the transactional replication is getting errors and failed. Is there relation b/n this replication failures and log growth in subscriber db?
I am Having trouble trying to set up SQL Server Replication Utilising Web Synchronisation Where the IIS(Web Server) is on a separate machine to the SQL Server(Publisher). I am using MSDE as the SQL Server Box, however even when I used SQLServer2000, or SQLServer2005 I have had no joy with the 2 separate Servers setup.
If I have the one server then I have no problems (i.e. One Server Setup) Server A: Windows 2000, with MSDE installed enabled for Merge replication, and has a Publication set up. IIS Web Page Setup for Synchronisation
My SQL Server 2005 Mobile device syncs via the web page on ServerA Fine, no problems at all.
The Trouble is when I am trying to utilise SQL Server Replication as follows. (i.e. 2 Server Setup)
Basically I am using the Same ServerA as in the one Server setup I had above. All I have done is I am now using a Separate IIS Server for the Web Synchronisation ServerB I have run the "Configure Web Synchronisation Wizard"(ConnWiz30.exe) on my web page on ServerB. And I am using Anonymous Access Authentication With Windows NT Authentication on my Web Server(ServerB), the Anonymous User is a Domain user, and is the Same Domain User I used in the One Server setup which I had working (so this IIS Anonymous Domain user should have all permissions required on the ServerA (SQL Publisher) both Windows permissions and SQL Server Permissions.
Server A: Windows 2000, with MSDE installed enabled for Merge replication, and has a Publication set up.
Server B: Windows XP, IIS Web Server(Web page enabled for Web Synchronisation)
I have a Mobile device as a subscriber, which is using Web Synchronisation on ServerB(Web Server), to sync with the ServerA (MSDE Box). The error I am receiving is "A Call to SQL Server Reconciler has Failed" Try to resynchronise, "The Process Could Not deliver the Snapshot to the Subscriber"
A little extra info: -I can remotely connect from my Web server(ServerB) to the SQL Box ServerA via a TCP/IP ODBC connection so remote connections does not seem to be an issue.
-If on My Mobile device if I try to Add a Subscription & Synchronise the replication using the AddSubscription(AddOption.ExistingDatabase), it works fine. (Obviously the subscription database does exist before the synchronisation)
If I try to Add a Subscription & Synchronise the replication using the AddSubscription(AddOption.CreateDatabase), I get the error as mentioned.
Is there something I have missed? Any help you can provide is much appreciated.
I am unable to install 32-bit SQL Server Integration Services on the server due to something that was left behind by the 64-bit version.
I've uninstalled SQL Server 2005 64-bit and when I try to install the 32-bit version of Integration Services, I get this error: "Failed to install and configure assemblies C:Program Files (x86)Microsoft SQL Server90DTSTasksMicrosoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087 Error message: Unknown error 0x80131501 Error descrition: FATAL: Could not find component 'Microsoft.SqlServer.Dts.Task.MessageQueueTask.ServCompMQTask' we just installed."
I can't seem to figure out how to resolve this problem with the COM+ and I can't remember if Integration Services is required.
I have documentation in the form of extended properties for tables which are subscribers in a replication scheme. The documentation describes the tables in reference to their replication scheme. I don't want to apply them to the source and have them published.I can't apply the extended properties receiving the error, 'don't have permission' yet I am DB creator on all systems. The theory is that I can't modify the subscription. Which makes sense.Can I turn off the replication, apply the extended properties, then turn on replication without causing harm?
SQL Server 2005 Standard Edition act as publisher and distributor. All subscribers are SQL Server 2005 Express Edition. According to 2005 book online, "MSMerge_History table exists in distribution database". Howevey I found this table in Subscriber database which is in SQL Server 2005 Express Edition. The problem is this table (MSMerge_History) and other two tables (MSMerge_genhistory, MSRepl_errors) are quite large. We want to keep SQL Server 2005 Express database as small as possible so we can put more data into it. Is there anyway (Manually or automatically) to clean those tables in SQL Server 2005 Express? Please help.
Can't connect to local server instance MSSQLSERVER in SQL Server Management Studio (SQL2005 sp2/Vista).
SQL Server Configuration Manager reports SQL Server2005 services: SQL Server (MSSQLSERVER) Running. This would indicate the name of the SQL server is "MSSQLSERVER" correct? I chose "default" instance during the install and that is the name it gave itself.
I tried connecting to the server using the following for the Server Name: MSSQLSERVER and .MSSQLSERVER neither works.
The only thing that works for my installation is just plain "." (no quotes) and nothing else. Can this be correct because I can't find any reference to this. Thanks.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Mi...mp;LinkId=20476
Hi Guy's, I have 2 questions:1. When I setup roles, a aspnetdb.mdf file is created automatically. Can I use the same database for any other / new table which is needed in my solution or do I need to create a second database?2. My hosting company does not support mdf files and there is no mdf attach tool available as well. Can someone explain to me how I get the mdf database into the SQL2005 Server and is there anything I need to change afterwards (connection strings etc.)? Thanks a lot in advance
I need to access object from Oracle 9i. I've installed O9i client on sql server and create linked server to O9i db. but when executing
exec sp_tables_ex N'SUN920' ---> list of all table appear
and when selecting from a prticular table -- got below msg
Msg 7314, Level 16, State 1, Line 2 The OLE DB provider "OraOLEDB.Oracle" for linked server "sun920" does not contain the table ""shm"."x"". The table either does not exist or the current user does not have permissions on that table.
I just upgraded my sql2000 server (3gb Ram,2 x2.4ghz p4xeon processors) to sql2005 64 bit (4gb ram,1 x dual core 2.0 xeon processor) The single processor is supposed to be faster than the previous dual processors combined.
The problem is now I am having major performance problems, the queries are lagging pretty badly intermittently.
What steps should I take to resolve this? I am planning on upgrading to 8gb of RAM tonight or tommorow as a 'throwing hardware at this problem without really knowing what I'm doing approach.'
I am not very good with perfmon, but if you want any stats from there please let me know. I'm googling now what I should be checking for.
I can't figure out why its actually running worse, these problems got worse after I set a maintenance plan to run last night which did backups, reindex all the stuff etc... It failed after 2 hours and I woke up to horrible performance this morning.