Replication size limitations?

  • I'm testing our "Pull data from SQL 2008 to SQL 2000" solution.

    It seems that I am having some trouble getting some fields with length 1000 characters (nchar) to replicate. The rest of the data comes across but these nchars are blank.

    Is there a data limit that I am not aware of, or is this a failing of SQL 2008 being pulled to SQL 2000?

    Test table structure -

    CREATE TABLE [dbo].[tblBench4](

    [id] [numeric](18, 0) NOT NULL,

    [testinga] [nchar](1000) NULL,

    [testingb] [nchar](1000) NULL,

    [testingc] [nchar](1000) NULL,

    CONSTRAINT [PK_tblBench4] PRIMARY KEY CLUSTERED

    (

    [id] ASC

    )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

    ) ON [PRIMARY]

    Data comes across with just the ID field populated. I thought the limit was much higher than the data going through that tiny test.

    I'm going to see if the same applies heading from 2000 to 2008.

  • The only limit that I know of is the record limit for SQL 2000. That is 8060 bytes. You have three nchar(1000). That comes to only 6000 bytes and you have only one more field that is numeric. So it should not go over that limit.

    Edit : Merge replication has a limit of 6000 Characters and transactional replication has a limit of 8000 characters.

    -Roy

  • NOTHING TO SEE HERE KIDS.

    The data WAS arriving. I was being lazy and using the GUI to view the table contents and it wasn't displaying despite the fact it was storing it. Some bug on 2000.

    CASE CLOSED.

    (Thanks for reply)

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply