How to move a large table with images to another SQL database and link it.

  • Query on view will hit main database every time. Will it not consume the bandwidth? I believe that’s the main issues here.

  • Dev (1/12/2012)


    Query on view will hit main database every time. Will it not consume the bandwidth? I believe that’s the main issues here.

    Bandwidth is network. I don't believe the issue is network related. I believe it is disk related, specifically I/O or disk controller problems. If that's the case, no solution is going to get around the problem except fixing the hardware problem.

    But the OP needs to run PerfMon and do some other tests to verify hardware issues.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • It could be a hardware issue but my question is still valid. If I query (or backup) on database with images, I shouldn’t expect much performance. OP mentioned he is trying to copy the backups via RDC (which is absolutely bad idea) it will definitely hit the network badly even if hardware is good.

  • Brandie Tarvin (1/12/2012)


    I think Paul has it right that the OP should consider using a view rather than actually moving the data.

    Hello other part of the discussion. I agree with the things Gianluca has said here (view/synonym/separate file group). I would just add that there is lots of good information about file backups in Books Online. Once it's set up, it's actually quite easy to administer, though some of the more advanced uses require Enterprise Edition (and they don't seem to be needed here).

  • Dev (1/12/2012)


    It could be a hardware issue but my question is still valid. If I query (or backup) on database with images, I shouldn’t expect much performance. OP mentioned he is trying to copy the backups via RDC (which is absolutely bad idea) it will definitely hit the network badly even if hardware is good.

    Only the non-image data is required remotely, if I am reading the posts in this thread correctly. Presumably, the vast bulk of the database size is in the images.

  • Yup, I missed that part but not entirely. OP didn’t mention it explicitly but it’s a fair assumption and I agree with you.

    I probably put myself in his shoes (or pulled him in my shoes) because I had the same requirements & client was more interested in images than rest.

  • Yes, only non-image data required. We don't want to copy often, just for support now and then.

  • Dev (1/12/2012)


    Yup, I missed that part but not entirely. OP didn’t mention it explicitly but it’s a fair assumption and I agree with you.

    edit: Ah! I see: you meant assuming that the image data would be the bulk of the database...yes I was assuming that. Sorry!

Viewing 8 posts - 16 through 22 (of 22 total)

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