InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 24 May 2012 12:53:37 GMT20http://www.sqlservercentral.com/Forums/Topic1305373-291-1.aspxI have setup mirroring between my local and DR sites.Thanks to everyone on here for your help.It's working fine so far, but my boss stated that they normally use the DR site to test the DB patches that come out. These patches are for the DB vendor (UltiPro) and come out pretty often.Due to budget reasons (long story) we are forced to use the newly mirrored DR site to test the Ultipro patches/updates.So, I will have to disable the mirroring on my DR site, then run the patches, then patch the prod server, then re-enable mirroring.How do I re-enable the mirroring on the remote/DR box? Will it sync back up to prod? or will I have to do the entire mirroring setup process again?Wed, 23 May 2012 14:32:33 GMTkrypto69http://www.sqlservercentral.com/Forums/Topic1304569-291-1.aspxI have a local site (production) and I have a DR site located many states away.Thanks to the help from this site, I setup mirroring. Which worked fine until I had huge amounts of inserts, which bogged down the server too much.Company won't pay for 2005 Enterprise edition (x2) to setup async mirroring. So, bottom line I can't mirror. Can't do merge replication, cause I can't change schema at all.What are my options? I was even thinking about writing a SSIS package to move the data once a day and restore daily..obviously not preferred.Tue, 22 May 2012 15:17:31 GMTkrypto69http://www.sqlservercentral.com/Forums/Topic1304734-291-1.aspxDear All,We are using Sql server 2005 standard eddition.We aer maintaining Transactional replication with update.We are observing Msreplication_queue is increasing.Row count is decreasing and increasing but size of table space is increasing only.Same time we are observing Temp DB space is increasing continuously.Please help me to find out the root cause and solve this issue.Thanks in advance.Wed, 23 May 2012 01:14:25 GMTMinto Minto(quendans)http://www.sqlservercentral.com/Forums/Topic1304409-291-1.aspxHi Guru,Currently, I have a peer replication running on domain1 for serverA to serverB. On domain2, I have new peer replication up and running for server C to server D. I copied backup files from domain1 to setup replication for testing.We are going to do cutover in a few weeks time. My plan is to get latest backups from domain1 and restore to domain2.What do I have to do first before I restore databases on domain2? Do I have to stop replication agents, or pause replication or break replcation and start over again?Thanks much for your advice.Tue, 22 May 2012 12:37:29 GMTAttopeuhttp://www.sqlservercentral.com/Forums/Topic1304321-291-1.aspxHi,I'm setting up mirroring between my local location and a DR site. The DB I am mirroring is 50Gig in size.I have setup mirroring on all my (smaller) instances between these two servers. Everything went just fine.BUt on this intance it gives me a 1412 error :The remote copy of database has not been rolled forward to a point in time that is encompassed in the local copy of the database log. (Microsoft SQL Server, Error: 1412)So, I figured the tlogs have been backed up (every3 hours) since I started the very long file copy process. It takes about 4 hours to move the data and log bak files. I tried taking a seperate backup of the tlog and then transferring just the log. I then restore just the log and it's still not in sync! Geez.. I've tried replaying the logs and still get the 1412 error. Help I'm outta ideas..Tue, 22 May 2012 10:53:27 GMTkrypto69http://www.sqlservercentral.com/Forums/Topic1301589-291-1.aspxHiWho can create replication starting from publisher and subscriberother than administratorThanksThu, 17 May 2012 03:49:42 GMTpmadhavapeddi22http://www.sqlservercentral.com/Forums/Topic1301885-291-1.aspxHello All, I am trying to set transactional replication. Publisher and distributer are on the same server, which is SQL2005. Subscriber is SQL2008. I am getting version compatibility error. I don't want to install SQL 2008 management studio to set replication. what are the other option I have?Thu, 17 May 2012 09:47:17 GMT2cool222http://www.sqlservercentral.com/Forums/Topic1301055-291-1.aspxHi,Just started a new job. They have a SQL server local and a DR SQL server in another state. both boxes are SQL2005.This is an accounting firm and they do end of month batch type of operations. So at the end of a bliing cycle there could be huge numbers of transactions all at once.Will transaction replication be able to handle this batch type of transactions? The pip between the two locations is a fat one with low ping times. What kind of tests do I need to preform prior to setting up transactional replication? (that's assuming transactional replication is best..??)If we have a hurricane and have to shut down the server here, will that break the remote DR server?Wed, 16 May 2012 07:59:06 GMTkrypto69http://www.sqlservercentral.com/Forums/Topic1300135-291-1.aspxHi Guys, Wonder if you could help me.To provide scenario, we want to replicate tables from our OLTP server to a reporting server so that internal users are able to query data safely.We have 2 databases which we want to replicate tables from, so DB1 and DB2 both on OLTP server (distribution database also on OLTP for now).All tables then go to our subscriber database on reporting server.This seemed to work fine until I have come across a problem when I wanted to replicate a table named ‘service’ on DB1 and another table also called ‘service’ on DB2 (going to same subscriber database).When I do this I then get an error message: Procedure or function sp_MSupd_dboService has too many arguments specified. (Source: MSSQLServer, Error number: 8144)To try get round this I renamed the destination object by changing the ‘destination object name’ in article properties so that the ‘service’ table replicates to the table DB2_Service in the subscriber database. I then reinitialised creating new snapshot.However when I do this, I still get the same error message.For now, I have removed the ‘service’ table from the publication on DB1 and everything is OK again. However, would someone be able to advise where I am going wrong here? I’m assuming there is something else I need to do to get round this problem.So you know both servers are SQL 2005.OLTP: 9.00.4266.00 SP3 Standard Edition (64-bit) (Long overdue for service pack I know)Reporting: 9.00.5000.00 SP4 Enterprise Edition (64-bit)Any advice would be greatly appreciated.Cheers, SamTue, 15 May 2012 04:56:56 GMTSam -480699http://www.sqlservercentral.com/Forums/Topic1299332-291-1.aspxHi All, I am so confused about configuring connection string when we want to configure db mirroirng or replication. how application will detect that it needs to send the connection to new (failover) server? might be a silly questions for all the gurus out there... please adviseSun, 13 May 2012 21:11:47 GMTDBA_AUShttp://www.sqlservercentral.com/Forums/Topic1299308-291-1.aspxcan someone please point me in right direction (links to articles) i would like to impelment peer to peer replication with 2 nodes and allowing writes to be performed on only one node.Sun, 13 May 2012 17:57:33 GMTDBA_AUShttp://www.sqlservercentral.com/Forums/Topic1130135-291-1.aspxSQL 2005 Enterprise SP2I will start off with that I am relatively new to replication as I just started using regularly within in the past couple of months.We have snapshot and transactional replication setup for a single database to feed a couple of subscribers.One subscriber only needs a few of the tables with filters and a subset of columns from the database and it only needs this data every 24 hours so we went with snapshot replication for this since it was a small subset of data and only takes minutes to create the snapshot and apply it.The other subscriber needs all the tables and columns on a near realtime basis so went with transactional replication for this. There are millions of commands being pushed through here throughout the day and night.This seems to work pretty well, but the problem we have seen since adding the snapshot publication is that between the time the snapshot has been generated and the next one is generated, the distributed commands from the transactional replication are not purged by the distribution cleanup history job. With all of these commands sitting in the database, we see an increasing decline in performance distributing new commands to the subscriber. We found this out the hard way at first because we had not generated a snapshot in a few days because it was still being tested and our distribution grew 50GB overnight and the transactional replication pretty much screeched to a halt which was quite alarming. It does appear, however, that once the snapshot is generated the next time, the previous transactional commands do get purged.I went through the procedures for the cleanup and it seems to me that having 2 publications on the same database isn't really accounted for.I searched the web for posts dealing with this issue and didn't really come across much.I'm wondering if anyone has seen this issue before and if they have any suggestions.Wed, 22 Jun 2011 23:14:37 GMTwillcullerhttp://www.sqlservercentral.com/Forums/Topic1297654-291-1.aspxHi all,I have created a new merge subscription to a pre-existing publication. The publication is partitioned, via article filters using the host_name value. Executing selects based on the article filters returns the expected set of data. The subscriber server is a clean db copy of the publisher, with no data. When I attempt to initialize the subscription, the synchronization monitor shows the following sequence of messages:Retrieving subscription informationThe process is waiting for a response from the query '{call sys.sp_MSget_subscriber_partition_id (?,?,?)}'The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout for the process. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.Then a sequence of Thread xx will wait... messages until finally the process fails with:The replication Merge Agent failed to retrieve subscription partitioning information from the Publisher. When troubleshooting, restart the agent with a higher value for -HistoryVerboseLevel and check the output log file for errors. Correct any database engine conditions that may be causing internal replication stored procedures to fail. When I look at the details for the new subscription in sysmergesubscriptions, there is no partition_id populated. The subscription has a status value of 0. No snapshot agent is created for the new subscription.I have tried to generate the partition via the publication properties > data partitions > generate the selected snapshots now option, but this just hangs.I've tried deleting the subscription and recreating it with the initialize immediately option, as well as using a script to generate the subscription and then attempting to initialize on first sync. The "automatically define a partition and generate a snapshot if needed when a new subscriber tries to synchronize" option is checked. Same problem each time.I'm new to replication. Clearly I've got something wrong in the initial setup. Any advice as to where to look would be appreciated.Regards, IainThu, 10 May 2012 01:31:20 GMTirobertsonhttp://www.sqlservercentral.com/Forums/Topic1291326-291-1.aspxHi I have replication set up between two servers, but I notice every time the job named "Distribution clean up: distribution" (by default) runs on the distributor, I get blocking issues where sp_MSadd_distribution_history called by the subscriber is being blocked by sp_MSsubscription_cleanup running on the distributor. Can anyone shed any light on why this is happening? ThanksFri, 27 Apr 2012 02:14:53 GMTjdrinkwaterhttp://www.sqlservercentral.com/Forums/Topic1296617-291-1.aspxIs this something that can be done? I have tried creating this by using sp_addsubscription, with @subscriptiontype = 3, which is an oledb provider. This does not seem to work. I am trying to do transactional replication from sql to a flat file.Thanks.Tue, 08 May 2012 10:30:32 GMTPankaj Sherehttp://www.sqlservercentral.com/Forums/Topic520342-291-1.aspxWhen I try and create a transactional replication publication I get the error shown below.Version: Microsoft SQL Server 2005 - 9.00.3042.00 (X64) Feb 10 2007 00:59:02 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2) NOTE: This error occurs when trying to replicate a single table!Any ideas on how to fix this?------------------------------Creating Publication- Configuring the Distributor (Success)- Creating Publication 'AnticsWebshop' (Error)MessagesSQL Server could not create publication 'AnticsWebshop'. (New Publication Wizard)------------------------------ADDITIONAL INFORMATION:An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)------------------------------Could not find stored procedure ''.Could not find stored procedure ''.Changed database context to 'Antics'. (Microsoft SQL Server, Error: 2812)For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=2812&LinkId=20476- Adding articles (Stopped)- Starting the Snapshot Agent (Stopped)- Generating a script file (Stopped)Thu, 19 Jun 2008 23:21:25 GMTDale Burrellhttp://www.sqlservercentral.com/Forums/Topic1293152-291-1.aspxI am trying to setup transactional replication from server A to server B.Server A is created by using Image of similar machine but with different name. I change name with sp_dropserver and sp_addserver. when I do select @@server, I get the right name. I checked in sysservers table and sever ID is set to zero. sqlserver is installed with domain account.When I setup replication I get error 'distributor is not configured right'distributor and publisher is on the same server. can some one help ?Tue, 01 May 2012 07:30:53 GMT2cool222http://www.sqlservercentral.com/Forums/Topic1285555-291-1.aspxDear All,We are using Sql server 2005 stsndard eddition.We aer maintaining Transactional replication with update.Form 3 days onwards we are observing MSrepl_commands is increasing.And the jobs are running fine.It is having 1 croe records.Due to this disribution DB size is increasing.Please help me to find out the root cause and solve this issue.Thanks in advance.Wed, 18 Apr 2012 05:35:35 GMTMinto Minto(quendans)http://www.sqlservercentral.com/Forums/Topic1294778-291-1.aspxThis morning I made some changes to an existing publisher.Original Publisher had 15 tables being replicated using Transactional replication. I edited the articles and unchecked 6 tables and saved the publication. Everything continued to run fine.I created a new Publisher with the 6 tables I removed and setup the do not replicate DELETE statements for these tables. I created the subscriber to the same subscriber the tables were pointed to on the Original Publisher. I created the snapshot and the New Publication was applied without error.Then about an hour after I set it up I started getting "Replication failed. Violation of PRIMARY KEY contraint. Cannot insert duplicate key in object".The error is on one of the tables I moved. The Primary Key is a GUID on the table in question.We reintialized the New Publisher and the errors went away for about thirty minutes and then came back.Does anyone know if there is any phantom articles or pieces from the Original Publisher causing problems? Or does anyone have ideas on what could cause this primary key problem or how to troubleshoot?ThanksgbThu, 03 May 2012 10:15:55 GMTsqlsponge2http://www.sqlservercentral.com/Forums/Topic585557-291-1.aspxHello, am cate.I accidentally deleted the distribution database after i had created a publisher, which also acted as the distributor. My problem now is that i cant even delete the existing publications, and neither can i create a new publicationTue, 14 Oct 2008 09:19:08 GMTkerusyhttp://www.sqlservercentral.com/Forums/Topic1292782-291-1.aspxPlease provide information about automating & scheduling scripting of existing replication environment?Thanks in advance,Regards, AnkurMon, 30 Apr 2012 13:45:54 GMTankur_librahttp://www.sqlservercentral.com/Forums/Topic1287264-291-1.aspxHello Friends..I need your help in getting some information about Golden Gate SQL Server replication. Could you guys please help me in finding an answers on how a highly transactional sql server does with clustering and replication ? How long does it take to get replica online to users ? Is there any good reading material about Golden gate sql replication? Please helpFri, 20 Apr 2012 09:29:24 GMTsqlquest2575http://www.sqlservercentral.com/Forums/Topic1291684-291-1.aspxWe have transactional replication as a push (A -> S, B -> S, C->S ), where ther are a series of views on S, based on multiple replicated tables from different sources (select from tables sourced from A, B, C). When I re-create replication from A -> S (we backup and restore from production to development servers, requiring us to drop and later create replication), it won't let me because it says that there are views dependent on those tables.Is there a way to define the view so that it's not looking to see if the tables it uses are there?Fri, 27 Apr 2012 10:05:31 GMTandre.quittahttp://www.sqlservercentral.com/Forums/Topic1290547-291-1.aspxTransactional Replication - The initial Snapshot ran for 5 hours during which time the Transaction Log went full although hourly Log backups ran successfully.My understanding is that committed transactions are written to the Distribution Log and I would expect there to be no influence on the DB's Transaction Log. In reality it looks like, when starting replication it puts a "lock" on the transaction log until the next Log Reader completes. Can anyone help with an explanation of the internal workings?Thu, 26 Apr 2012 04:47:02 GMTgreg.lynchhttp://www.sqlservercentral.com/Forums/Topic1290564-291-1.aspxDear All,I have created the Replication both on the Publication Server and the Subscriber Server without any problem, but after the Subscriber is created, I'm not able to see the Subscriber. I've checked in the Replication Monitor-> All Subscriptions->Then right clicked on the Subscriber-> View Details, in the "Actions in the selected session window" the massage states that the "The process could not connect to Subscriber 'servername'". In the Error details window, it gives the following error message:The process could not connect to Subscriber 'Servername'. (Source: MSSQL_REPL, Error number: MSSQL_REPL0)Get help: http://help/MSSQL_REPL0Named Pipes Provider: Could not open a connection to SQL Server [53]. (Source: MSSQLServer, Error number: 53)Get help: http://help/53A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (Source: MSSQLServer, Error number: 53)Get help: http://help/53Login timeout expired (Source: MSSQLServer, Error number: HYT00)Would anyone let me know what might be causing the issue because I'm able to connect to the ServerThank you in Advance!Thu, 26 Apr 2012 05:14:18 GMTtt-615680http://www.sqlservercentral.com/Forums/Topic1288559-291-1.aspxHello!I have very serious problem by transactional replication attempt.By creating snapshot it can't create initial snapshot. After some time running the snapshot agent and creating some files, it throws "Failed to read from server" never succesfully creating snapshot till the end.Database is working ok, but it couldn't create snapshot on 2 different servers (one is Win2000 other is Win2008, SQL 2005 SP3).I tried with assigning all possible permissions but don't think it matters because other DBs on the same server (same repl.folder also!) are created succesfully..Do you have any clue, I run out of ideas??Joško[b]ERROR MESSAGE:[/b]Error messages:Message: Failed to read from serverStack: at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.ThrowNativeBcpOutException(CConnection* pNativeConnectionWrapper) at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.BcpOut(String strBcpObjectName, String strBcpObjectOwner, String strBaseBcpObjectName, Boolean fUnicodeConversion, String strDataFile, String strLoadOrderingHint, String strWhereClause) at Microsoft.SqlServer.Replication.Snapshot.SqlServer.BcpOutThreadProvider.DoWork(WorkItem workItem) at Microsoft.SqlServer.Replication.WorkerThread.NonExceptionBasedAgentThreadProc() at Microsoft.SqlServer.Replication.WorkerThread.AgentThreadProc() at Microsoft.SqlServer.Replication.AgentCore.BaseAgentThread.AgentThreadProcWrapper() (Source: MSSQLServer, Error number: 0)Get help: http://help/0Message: Error converting data type nvarchar to float.Stack: (Source: MSSQLServer, Error number: 8114)Get help: http://help/8114Mon, 23 Apr 2012 16:37:19 GMTjosko 8074http://www.sqlservercentral.com/Forums/Topic571883-291-1.aspxHi I am having issues with deadlocking. I am running a trace on profiler and receiving a deadlock graph. Using the associated object id and the following querySELECT object_name(object_id)FROM sys.partitionsWHERE partition_id = 72057594066173952it gives me MSReplication_subscriptions as the culprit??I have no idea how to resolve this issue. It is only replication spids that are being deadlocked. Surely replication should not allow this.I have also made sure that no articles are duplicated across the subscriptions but am at a lossAny advice would be appreciatedthanksChris Thu, 18 Sep 2008 09:30:40 GMTWedge78http://www.sqlservercentral.com/Forums/Topic957735-291-1.aspxIn the publication table, there is a field 'create_timestamp' which is a bigint and has default value '(@@dbts+(1))', I use this field to sync with local SQL CE, but if add the field to publishing articles , the Microsoft sync framework can't run well. any one know the mechanism of Microsoft Synchronization ? for solve the above problem , I add a new field 'create_timestamp' in the subscription table instead of publishing the field 'create_timestamp' , it works fine. but when I run a snapshot to the subscriber , the added field 'create_timestamp' will be losted , is there any way to keep the 'create_timestamp' field and its value existed or can be restored after snapshot ?Thanks in advance.Thu, 22 Jul 2010 21:45:37 GMTmy990cnhttp://www.sqlservercentral.com/Forums/Topic1287247-291-1.aspxHi all, Any ideas as to how I remove a script from replication, i.e. the opposite of sp_addscriptexec? Unfortunately, I don't seem to have an sp_dropscriptexec :-)Is it even possible to view a list of scripts to be executed? I have a \SCRIPTS folder in my snapshot folder, the script I want to remove is in there. I've tested just removing the script from this folder, but replication still tries to run it, so it must be held somewhere else?I'm a relative novice when it comes to replication btw, as might be apparent from this post...Regards, IainFri, 20 Apr 2012 09:19:18 GMTirobertsonhttp://www.sqlservercentral.com/Forums/Topic1286355-291-1.aspxHi,Now I KNOW this is a problem which is featured somewhere on here and I have seen it in a couple of other places BUT I need to get some clarification and an idea of what direction I need to be heading in because the answers I have seen simply don't fit with what I am experiencing so - phew - here goes:PART 1:A. Server A - Transactional Repl -> Server B = A OkB. Server A - shutdown and restart. Transactional Reply X not ok because of: "A required Privilege is not held by the client".- I have NOT changed the service account.- I have NOT changed the account that replication uses.- ALL that happened was that the publisher was stopped and restarted.- Replication will now ONLY work if the SQL agent is set as "Local System".PART B:Upon attempting to troubleshoot part A I set up transactional replication on another server - THAT I HAD USED FOR THIS PREVIOUSLY and had NOT changed since then.Though this server uses a different SQL Service account it uses the same replication account.A. This fails due to an "Unknown Security Error".B. ALL other AD accounts that I try fail in exactly the same way.- Replication will now ONLY work if the SQL agent is set as "Local System".SO:- YES, I have tried making all account server administrator and SQL Administrator and have tried once having added them to the relevant SQL groups on the server.- YES, I have tried different accounts on different servers - always the result is the same.- NO, this was not happening before.Does anyone having ANY suggestions, suggestions that do NOT involve "changing the SQL Agent account" because I stated I have:A: tried this andB: have never had to before.Thank you very much.Thu, 19 Apr 2012 06:27:50 GMTbass.munkeehttp://www.sqlservercentral.com/Forums/Topic348718-291-1.aspxHi,I need to synchronize the data between two SQL Server 2005 Express.The database is really simple, just few tables (but data are inserted very often) without any triggers.Since Express edition could not behave as a Publisher I was thinking about implementing manually a sort of Replication mechanism... It should be a sort of Transactional Replication with queueud updating.Does it sound a good idea?Has anyone done this before o there are better solution?Thanks in advance,StefanoFri, 02 Mar 2007 02:48:00 GMTste72http://www.sqlservercentral.com/Forums/Topic1286236-291-1.aspxWe have a couple of tables have XML data types columns running on Standard edition of sql server 2005 SP3, wondering ifwe can replicate those tables in transaction replication with update subscriber ? Thanks.Thu, 19 Apr 2012 01:06:47 GMTawuhttp://www.sqlservercentral.com/Forums/Topic639734-291-1.aspxIn a SQL Server 2005 transactional replication with the distribution database on the same system as the publisher I keep getting the above mentioned errors for which I cannot find any helpful information (needless to say, the links below are blank...)[font="Courier New"]The process could not execute 'sp_replcmds' on 'SRVDB01\SQL2005'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)Get help: http://help/MSSQL_REPL20011Unspecified error (Source: MSSQLServer, Error number: 0)Get help: http://help/0The process could not execute 'sp_replcmds' on 'SRVDB01\SQL2005'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)Get help: http://help/MSSQL_REPL22037[/font]I have deleted the publication and the subscriber and re-created them "from scratch" - the errors persists.Can anybody please provide me with additional information and suggestions what to try to get the replication running again? Thanks a lot in advance!Tue, 20 Jan 2009 02:37:10 GMTSwiss-Alhttp://www.sqlservercentral.com/Forums/Topic767965-291-1.aspxHi,We got Publisher and Subscrber on W2003 R2 with SQL Server 2005 Ent. SP3 CU#1This is simple replication were Distributor as well Log Reader agents are on Subscriber.Yesterday we got following errors in Log Reader, and it unable to start it.Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on 'PUBLISHER'.'.Status: 0, code: 18773, text: 'Could not locate text information records for the column "COLUMN_NAME", ID 16 during command construction.'.Status: 0, code: 18805, text: 'The Log Reader Agent failed to construct a replicated command from log sequence number (LSN) {00034a38:000002d4:0055}. Back up the publication database and contact Customer Support Services.'.Status: 0, code: 22037, text: 'The process could not execute 'sp_replcmds' on 'PUBLISHER'.'We found a lot of KB articles, but non of them are for this version or patch level.- KB 952330 as a Product bug and resolved in Service Pack 2 Cumulative Update 8. We got higher version of SQL Server- KB 276281 as a Product bug but in SQL Server 7.0. Resolved by a hot fix. We got different version of SQL Server.- KB 958684 as a Product bug and resolved by apply CU1 for SQL Server 2005 SP3. We already got that version.- KB 933519 as a Product bug and resolved by apply CU2 for SQL Server 2005 SP2. We got higher version.- KB 971136 as a Product bug and resolved by apply SP1 for SQL Server 2008. We got different version of SQL Server.Any ideas? :)Mon, 10 Aug 2009 09:50:51 GMTlazarusekhttp://www.sqlservercentral.com/Forums/Topic1283161-291-1.aspxDear All, I'm having an odd problem and I'm stuck on what else to do, I have a stored procedure which runs the Report in Reporting Services. The Stored Procedure Executes fine in SQL Server Engine but when I try to run the Stored Procedure in Reporting Services it throws the following error: An error occurred during client rendering.An error has occurred during report processing.Query execution failed for dataset 'DataSet2'.Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. My understanding is that if there are no issues when the Stored Procedure is executed then it should be fine in Reporting Services, as the Data is coming directly from SQL Server; unless I need to do something else in Reporting Services? Thanks in advance!Fri, 13 Apr 2012 08:00:56 GMTtt-615680http://www.sqlservercentral.com/Forums/Topic1283013-291-1.aspxDear All, When selecting Articals to Replicate, I know there is an option under "Filter Rows" where we can filter out columns through sql query script; but I was wondering if there is any way of filtering out two or more tables please? Thank you in advance!Fri, 13 Apr 2012 04:42:30 GMTtt-615680http://www.sqlservercentral.com/Forums/Topic1282362-291-1.aspxI have two SQL Server 2005 Servers. The Servers are in different Networks with a hole poked through the firewall to allow certain traffic. One Server is at a hosting company and one Server is on our Home Network so they are in different domains. My dilema is this. I have a Database on the HOME office SQL Server and I need to replicate a few tables back to the SQL Server at the hosting company. The requirement is that the Subscriber (at the hosting company) PULL the changes from the Publisher. I am having a hard time figuring out how to set up the Security at the Subscriber. It wants a Domain account for the Distribution Agent Process AND the Connection to the Subscriber must impersonate the Distribution Agent Process account. [b] Does this mean I cannot do PULL subscriptions in this setup? [/b] Because the Subscriber and Publisher are in different domains - I do not have a Domain account that is the same at the Subscriber AND the Publisher.Thu, 12 Apr 2012 07:33:11 GMTJpotucekhttp://www.sqlservercentral.com/Forums/Topic1280624-291-1.aspxWhile configuring the replication following error message is appearingInvalid destination path C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data.Changed database context to 'master'. (.Net SqlClient Data Provider)------------------------------For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=14430&LinkId=20476------------------------------Server Name: GMSERVERError Number: 14430Severity: 16State: 1Procedure: sp_adddistributiondbLine Number: 214We have also set permissions, but still not able to trace the error.Please HelpAmitTue, 10 Apr 2012 00:44:22 GMTamit.vasanhttp://www.sqlservercentral.com/Forums/Topic1281198-291-1.aspxHello,Currently, I have sql 2005 peer-to-peer replication running on two VM machines. We are planning to migrate these VMs(V2V) to new data center. The server names will remain the same but different IP, DNS etc.Here is what we are planning to do:1. DBA shut down both sql engine and sql agent2. Windows doing V2V migration then re-IP and DNS stuff and bring server online.3. DBA starts both sql engine and sql agent.What kind of things I need to prepare before this migration to happen?I am not sure I need to script everything just in case if something goes wrong, should I?Tue, 10 Apr 2012 15:40:52 GMTAttopeuhttp://www.sqlservercentral.com/Forums/Topic1280633-291-1.aspxHi Friends,We have three servers A, B, CA is used for UAT, B is used for Production and C is used for Mirroring.As a trial, we are able to setup the mirroring for the UAT SQL (Server A) with mirroring SQL (Server C) using the port 5022.Later we have removed the mirroring setup for UAT.Then when we have tried setting up the mirroring for Production SQL (Server B) with mirroring SQL (Server C), we got the below mentioned error. I would request if someone could help us out with resolution:The server network addredd "TCP://XXXXXXXX:5022" can not be reached or does not exist. Check the network address and that the ports for the local and remote endoints are operational. (Microsoft SQL server, error : 1418).Thanks in advance for help / resolution....Query A: Is it due to the reason that port 5022 is initially used for UAT database server mirroring and the same is not available now for Production server??Query B: is there any other setup missing while doing the mirroring for producton server.Additional input: We have already defined the service account of SQL server services as same for all the instances (UAT, Production, Mirroring).......Tue, 10 Apr 2012 00:58:02 GMTashwani.jain1