Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

Discussions on SQL Server Replication

older | 1 | .... | 151 | 152 | (Page 153) | 154 | 155 | .... | 181 | newer

    0 0

    TITLE: Microsoft.SqlServer.ConnectionInfo
    ------------------------------

    SQL Server could not configure 'SUL\HYD' as a Distributor.

    ------------------------------
    ADDITIONAL INFORMATION:

    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

    ------------------------------

    An error occurred during the execution of xp_cmdshell. A call to 'CreateProcess' failed with error code: '5'.
    Destination path C:\Program Files\Microsoft SQL Server\MSSQL11.HYD\MSSQL\Data is not valid. Unable to list directory contents. Specify a valid destination path.
    Changed database context to 'master'. (Microsoft SQL Server, Error: 15121)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.2100&EvtSrc=MSSQLServer&EvtID=15121&LinkId=20476

    ------------------------------
    BUTTONS:

    OK
    ------------------------------



    What is the Solution for this Problem ??



    0 0

    Hi Friends,

    We have transactional replication configured in our environment. We remove replication and install it again during db refresh activity . Do we have system table which tracks the date when publications are created. I don't find that info in mspublications.

    Thanks

    Udhayan


    0 0
  • 03/25/16--15:33: ALTER TABLE not possible
  • Hi everyone,

    I've implemented Replication in my both instances Sql2k12.

    Publication type is Snapshot.

    Now, trying to modify some columns or constraint for any table I get this message (similar in each case):

    'EmployeeLogon (Acc)' table
    - Unable to delete index 'PK_EmployeeElectronicJournal'.  
    Cannot alter the table 'EmployeeLogon' because it is being published for replication.
    Could not drop constraint. See previous errors.

    Let me know which would be the upcoming steps in order to allow ALTER COLUMN/CONSTRAINT in my schema tables.

    Thanks for your time


    0 0

    We have a weekly snapshot replication job (pull) that creates snapshots every Saturday. The job at the subscriber runs continuously. When this job runs, the permissions given to users on 'ABC' table are lost, and we have to go back and grant the permissions manually every Sunday. The permissions on 'ABC' aren't tampered with in the Publisher. Then why are the permissions dropped on the subscriber when a snapshot is applied? This lack of permissions hampers business critically. Please advice.

    0 0

    Hi,

    I have a SQL Server replication with pull subscriptions. I have SP which creates a #Temp table for the data manipulations. Now I'm having a problem when doing this on the subscriber. It throws error

    "CREATE TABLE permission denied in database <DB Name>.".

    Is there any way I can allow this database to create a temp table.

    Please help,

    Thanks in advanced :)

    - Chama -


    0 0

    I'm in a case where I want to have a second copy of a database for reporting purposes, however the tables in the source database have no keys in them, and I can't change the structure of those tables by adding keys, hence transnational replication is not an option... thus the following are what I have in mind:

    • Log shipping: but this has constraints on the source and destination SQL Server instances versions to make the secondary database read only + the secondary database will be read only so I can't create indexes + security is a headache if I want to have some users to have read access to the secondary but not the primary.
    • Snapshot replication: the database is relatively big, and I see it a heavy process to create a snapshot for the whole database every night then overwrite the replica ... and I'm wondering if this will also overwrite the created indexes on the replica or not!

    Is there any other solution?


    0 0

    On my primary database:

      - I have setup Snapshot publication

      - Snapshot is generated directly on the DR server via UNC path

      - SQL Agent job generates snapshot every night at 10 pm. It takes approximately 30 minutes to generate the snapshot of 5 GB database.

     

      On my DR (Disaster Recovery) Server:

                    - I have setup pull subscription for the subscription database

    Currently, I have scheduled Subscription database to synchronize around 10:30 pm every night with the assumption that snapshot generation by Publisher will be completed by then.

    Instead, I want to kick off Subscription database synchronization as soon as the Snapshot generation is completed on the primary server. Is there any way to achieve this?


    0 0

    Hello,

    I am having trouble getting a pull subscription running.

    I have a main database with a publication on one machine (windows server 2012) (SQL 2014)

    I have a test database on another machine (windows 10) (SQL 2014)

    I have successfully managed to get a push subscription running from my publication database to my test database and this works fine.

    I would like to sync an offsite database with the main database via web, which will require a pull subscription.

    I have enabled web sync via IIS on the main database server. I have successfully verified that I can connect to the replisapi.dll via the web

    To start with I would like to test the pull subscription from my test database within the local network. I created the pull subscription from the test database (not using web sync at this point) and this created successfully. After creation the subscription does not appear to be running. No job is generated in the agent for this, and when I open the subscription properties, it states that the agent has never been run. The subscription is set to run continuously.

    I have tried dozens of times to get this working, including reinstalling SQL server. I noticed that under the replication folder in SSMS, there is no publication folder and there is no option to configure distribution.

    Any assistance to get running would be much appreciated. Help please...


    0 0

    Greetings. We need to retain the original TIMESTAMP value between the Publisher and the Subscriber. I'm aware that I can change a Publication property, but this only seems to be a viable option when the Subscription is initialized from a Snapshot. When the Snapshot occurs, I've learned that some magic is worked behind the scenes to make everything go. However, this isn't the case when initialized from backup/ restore.

    I've thought of many kludgey things, and even tried a few, to get around this issue. None of my options seem to be good ones. Is there a good way to handle this?


    Thanks in advance! ChrisRDBA


    0 0

    I have a snapshot replication that I have scheduled the synchronization every night by following the steps in this Microsoft link, where they said that you can configure that in the "New Subscription Wizard" in Synchronization Schedule tab.

    However, it does not seem it is working. The changes of yesterday is not reflected to the subscriber database today. I have checked the replication monitor and all the related jobs and agents but no errors!

    What could be wrong? ... I'm wondering if I had to "Schedule the Snapshot Agent to run at the following times" while creating the Publication! which I didn't ....


    0 0

    Hi all,

    I see from the feature comparison chart that SQL Server Express supports MERGE replication as subscriber only. We're setting up a new app and some systems need to be able to work from the local db so we are currently thinking of SQL Server Standard or Business available via VPN, and Express on the workstations / laptops that might be disconnected occasionally. If I understand correctly a subscriber will receive writes if the publisher is accessible and it does so by sending the writes to the publisher which then is replicated back to the client. 

    Is there a feature that will allow the changes to the local and perform the replication tasks when the publisher once again becomes available?

    TIA
    Mike


    0 0
  • 04/03/16--14:52: Subscription Already Exists
  • I am running SQL Server 2014 on Windows Server 2012 R2 Standard. The database server is setup to be both a publisher and distributor for replication out to several remote databases running on Windows 7. One of the remote computers running windows 7 had to be replaced. Once the new computer was setup and running, I deleted the existing subscription using SSMS. The new computer had to be named the same as the old computer that was taken out of commission. I tried to setup replication on the new computer and I get the following error.

    Cannot create the subscription because the subscription already exists in the subscription database. Only one subscription to the same publication is allowed in each subscription database. Drop the subscription and add it again if necessary. If the problem persists, replication metadata might be incorrect; see Books Online for troubleshooting information.
    Parameter 2 is incorrect for this DBCC statement.
    Supply either @credential_id or @credential_name.
    Changed database context to 'ScaleFusion'. (Microsoft SQL Server, Error: 14058)

    I have done this many times before without any issues. Now I have 4 machines behaving in the same way. I have tried to find information on how to address this issue but so far I have found nothing that has been of any help. Please let me know what I can do to fix this.




    0 0

    I set up one-way transactional replication on a subset of tables in a single db from 2008 R2 to 2014. It worked perfectly right off the bat, then after a few days, it simply died, deleting all the tables in the Subscriber db and throwing the following error message in the Replication Monitor:

    "The selected subscriber does not satisfy the minimum version compatibility level of the selected application."

    Publisher = SQL Server 2008 R2 Standard 64-bit, running on Windows Server 2012 R2 Standard.

    Subscriber = SQL Server 2014 Standard 64-bit, also running on Windows Server 2012 R2 Standard.

    All MS documentation and all forum discussions I can find clearly state that transactional replication between 2008R2 and 2014 is supported.

    As this is one-way replication fro Publisher to Subscriber, it is not set up as updatable.

    When things initially failed, all replicated tables in the Subscriber db were dropped. A couple of days later, some of them mysteriously reappeared -- with no records.

    Every time I try to create a new subscription now, I receive the same error message as above.

    TIA for any help.

    ______________

    EDIT:

    I tried running a script using sp_addsubscription and sp_addpushsubscription_agent to get around the issue, as I found another forum posting where someone else had a similar problem, and they tried this and it worked for them. It does not work in my case; While it successfully creates the Subscription, once I attempt to launch the Distribution agent, I get the same "The selected subscriber does not satisfy the minimum version compatibility level of the selected application" error.

    So I am once again back in the same situation: Setting up transactional replication between these two servers worked fine at first, then died, and now I cannot recreate it.


    0 0

    We have a transaction database, 50K Users log Business/Transaction information thorough out the day and run reports out of it.
    We don't have separate Reporting Database. Some time during the peak hours the load(IO) on the Database server is heavy.
    So we were looking to separate the Reporting Request (Data Reads) to different DB Server. What is the best way to do this. I see different methods but
    these three things getting confused.

    Could someone tell what is the difference between these three things and which one will good solution for us.

    Database Mirroring
    Replication (Itself have three categories)
        snapshot replication
        transnational replication
        merge replication
    AlwaysOn Availability Groups

    0 0

    Hi All,

    We have transactional replication in place for many databases in our environment. The requirement now is to implement TDE for whole database. I request you to share your thoughts and insights about considerations for TDE.

    Is there any impact on replication. If i apply TDE in publisher DB will there be any impact on subscriber DB?

    In our case we are going to implement it in both publisher db and suscbriber Db.

    Is compressed backup possible after applying TDE?

    We have SAN backups for our prod systems, anything that needs to be taken care in that front( can we expect increase in backup duration, backup size )

    Thanks

    Udhayan


    0 0

    We have CDC & Replication on same Database. When there are huge DML i.e. 30-40 million updates within 60 minutes the CDC is behind for 3+ hours. We wanted to tweak @maxtrans & @maxscans options as per the below article to improve performance however we cannot use  sys.sp_cdc_change_job to make the change as CDC is handled through replication. What are the alternate options available to make the change?

    https://technet.microsoft.com/en-us/library/dd266396(v=sql.100).aspx


    Thanks, Kranthi


    0 0

    I have replication between to SQL Server 2008R2 instances, but I'm getting this error on the "Distribution to Subscriber History" tab:

    Cannot update a timestamp column. (Source: MSSQLServer, Error number: 272)

    I tried:

    updatesysarticlesset schema_option= schema_option-(schema_option & 8)*where artid= 5

    as suggested in this Miscrosoft article

    but nothing changes ... same error :(

    I can't change the source INDEXED VIEW article nor I can change on the destination TABLE.


    0 0

    I have started getting an issue in replication where replication fails with the process could not initialise the subscriber always wins conflict resolver. Please verify the component is registered. I can not locate the cause of this error.

     

    I have even uninstalled all my SQL Servers and done a new install of SQL 2008 R2 x64

     

    Windows 2008 R2 x64 with SQL 2008 R2 x64

    Any help would be appreciated.


    0 0

    Hello Experts,

    i have to prepare a query in which after the where clause i want to say get me the name of database only if it ispreferred replica.

    i see there is a function which gives 1 if the passed database is prefered replica.

    but what i want is just oposite of it.

    where (SELECT [master].sys.fn_hadr_backup_is_preferred_replica('%') = 1)

    So i dont know the name of database but i always want to run my primary query only if it is prefered replica.

    is there a way to achieve it?


    -KAKA-



    0 0

    Hello!

    My ultimate question is, are there any known bugs having to do with replication on SQL Server 2012 SP3?

    We recently ran into a replication error that seemed odd.  When I looked into sp_browsereplcmds to find the error, there seemed to be two commands that it was trying to run at once as the same command. They both were attempting to replicate an identical large (227 KB) XML variable stored in an nvarchar(max) row to the subscriber and it looked something like:

    {CALL [dbo].[sp_MSupd_dboTableName] (,,,,,,N'<TheLargeXMLVariable>',,,,2016-02-04 22:12:59.453,{2080D901-8CC3-F511-B4CB-BD162D87DCE5},17914,0x4004)}
    {CALL [dbo].[sp_MSupd_dboTableName] (,,,,,,N'<TheLargeXMLVariable>',,,,NULL,{005B005D-003C-003E-2B00-700072006A00},6239248,0x4004)}

    These ended up being out of order and there was a NULL attempting to be updated into a column that did not allow nulls in either the subscriber or publisher DBs.

    We had recently upgraded these DBs from SP1 CU9 to SP3. 


older | 1 | .... | 151 | 152 | (Page 153) | 154 | 155 | .... | 181 | newer