Post reply

New or Existing Database

  • October 8, 2011 at 6:24 am

    #246099

    Hi,

    We're implementing a set of new features for our app and require dynamic creation of tables. My concern is that there will be lots of new data and I'm not sure if adding this new data to existing database is a good idea. However, there will be joins to existing tables. Would performance degrade in case of cross database joins?

    Thanks

  • October 8, 2011 at 2:59 pm

    #1392110

    Lexa (10/8/2011)

    Hi,

    We're implementing a set of new features for our app and require dynamic creation of tables. My concern is that there will be lots of new data and I'm not sure if adding this new data to existing database is a good idea. However, there will be joins to existing tables. Would performance degrade in case of cross database joins?

    Thanks

    Are the dynamically created tables going to be permanent or temporary? What are these tables being used for?

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • October 8, 2011 at 3:06 pm

    #1392112

    It depends 😀

    If the DBs are in the same instance, use the same collation and security context, have a similar layout of file groups (e.g. in terms of log file location) and maybe some more conditions need to be met then cross-DB-joins should not negatively influence performance.


    Lutz
    A pessimist is an optimist with experience.

    How to get fast answers to your question[/url]
    How to post performance related questions[/url]
    Links for Tally Table [/url] , Cross Tabs [/url] and Dynamic Cross Tabs [/url], Delimited Split Function[/url]

  • October 8, 2011 at 3:59 pm

    #1392121

    Jeff Moden (10/8/2011)

    Lexa (10/8/2011)

    Hi,

    We're implementing a set of new features for our app and require dynamic creation of tables. My concern is that there will be lots of new data and I'm not sure if adding this new data to existing database is a good idea. However, there will be joins to existing tables. Would performance degrade in case of cross database joins?

    Thanks

    Are the dynamically created tables going to be permanent or temporary? What are these tables being used for?

    Permanent, they will be used to join to already existing tables.

  • October 8, 2011 at 4:01 pm

    #1392122

    LutzM (10/8/2011)

    It depends 😀

    If the DBs are in the same instance, use the same collation and security context, have a similar layout of file groups (e.g. in terms of log file location) and maybe some more conditions need to be met then cross-DB-joins should not negatively influence performance.

    Yes, all the physical layouts of the groups will be the same, same collation and certainly the same instance.

Viewing 5 posts - 1 through 4 (of 4 total)

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