DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: To seperate applications and tablespaces?

  1. 09-21-2010, 10:38 AM #1
    ssmith
    ssmith is offline Senior Member
    Join Date
    Apr 2001
    Location
    Congleton
    Posts
    258

    To seperate applications and tablespaces?

    Is it a good idea to separate each application on a database into a separate tablespaces? We have several applications within our OLTP database, I think it is better to put all the small applications into one tablespaces, i.e. between 3-10 tables in each application. Others thinks it a good idea to separate each application in a separate tablespace, even if they only have 3 tables. What are the pros and cons of doing this? I would think the more datafiles the database has to open the more resources the server has to use. What does anyone else think? Rgds. Sheryl
    Reply With Quote Reply With Quote
  2. 09-21-2010, 12:31 PM #2
    PAVB's Avatar
    PAVB
    PAVB is offline Senior Advisor
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,555
    May I ask three questions?

    1- How big is your database - not taking into consideration system and temporary tablespaces.

    2- What kind of storage is hosting your datafiles?

    3- Are datafiles cooked-filesystems? raw-devices? asm?
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
    Reply With Quote Reply With Quote
  3. 09-22-2010, 03:41 AM #3
    davey23uk
    davey23uk is offline Senior Advisor
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,334
    Quote Originally Posted by ssmith View Post
    Is it a good idea to separate each application on a database into a separate tablespaces? We have several applications within our OLTP database, I think it is better to put all the small applications into one tablespaces, i.e. between 3-10 tables in each application. Others thinks it a good idea to separate each application in a separate tablespace, even if they only have 3 tables. What are the pros and cons of doing this? I would think the more datafiles the database has to open the more resources the server has to use. What does anyone else think? Rgds. Sheryl
    it makes no difference, a tablespace is just a tablespace

    go for what makes logical sense to you and makes it easier to support
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules

Click Here to Expand Forum to Full Width