Post Closed as "not a real question" by jcolebrand
3 improved formatting and corrected grammar.
source | link

I need to improve the performance of our entripriseenterprise .Net search application(.net) from the database point of view. The

The app already has 4 schemas on a separate sql serverSQL Server 2008.

  • 2 schemas for front-end operations ( the tables areconsisting of relatively small) tables.
  • 2 schemas for back-end indexing, processing etc. (the, many of these tables are very huge here)huge.

Front and back end schemas doesdo not share any foreign key relation between each otherrelationships. To

To be highly responsive during the day time, the backend operation run in night time only runs during the night.

Now the problem is theThe database server is heavelyheavily loaded at night time and often we get timeout errors. I I want to spread the backend operations through outthroughout the day to overcome this issue with. However, this has to have no impact on the front end operations. when i see

When I check the performance graphs, during daytime the server andday the DB in itSQL Server is very minimally usedunder light load.

My knowledge and expexperience on DBdatabase concepts is limited. Following

Following are the options which i thinkI've thought of.:

  1. I might not get a approval for 2 sql serverSQL Server machines.
  2. Front-end schemas in a separate DBdatabase on the same sqlSQL Server instance. Place the front DB in-end database on separate drive.
  3. Front-end schemas ison a separate filegroup., and place the filegroup inon saperateseparate drive.

Please let me know the pros and cons of my options and any other options which you think suits here. Thanks in advance.

I need to improve the performance of our entriprise search application(.net) from the database point of view. The app already has 4 schemas on a separate sql server 2008.

  • 2 schemas for front-end operations ( the tables are small)
  • 2 schemas for back-end indexing, processing etc. (the tables are very huge here).

Front and back schemas does not share any foreign key relation between each other. To be highly responsive during the day time, the backend operation run in night time only.

Now the problem is the database server is heavely loaded at night time and often we get timeout errors. I want to spread the backend operations through out the day to overcome this issue with no impact on the front end operations. when i see the performance graphs, during daytime the server and the DB in it is very minimally used.

My knowledge and exp on DB concepts is limited. Following are the options which i think of.

  1. I might not get a approval for 2 sql server machines.
  2. Front schemas in a separate DB on the same sql instance. Place the front DB in separate drive.
  3. Front schemas is separate filegroup. and place the filegroup in saperate drive.

Please let me know the pros and cons of my options and any other options which you think suits here. Thanks in advance.

I need to improve the performance of our enterprise .Net search application from the database point of view.

The app already has 4 schemas on SQL Server 2008.

  • 2 schemas for front-end operations consisting of relatively small tables.
  • 2 schemas for back-end indexing, processing etc., many of these tables are huge.

Front and back end schemas do not share any foreign key relationships.

To be highly responsive during the day time, the backend operation only runs during the night.

The database server is heavily loaded at night and often we get timeout errors. I want to spread the backend operations throughout the day to overcome this issue. However, this has to have no impact on the front end operations.

When I check the performance during the day the SQL Server is under light load.

My knowledge and experience on database concepts is limited.

Following are the options which I've thought of:

  1. I might not get a approval for 2 SQL Server machines.
  2. Front-end schemas in a separate database on the same SQL Server instance. Place the front-end database on separate drive.
  3. Front-end schemas on a separate filegroup, and place the filegroup on separate drive.

Please let me know the pros and cons of my options and any other options which you think suits here.

2 edited tags
| link
1
source | link

Multiple schema or multiple databases for better performance

I need to improve the performance of our entriprise search application(.net) from the database point of view. The app already has 4 schemas on a separate sql server 2008.

  • 2 schemas for front-end operations ( the tables are small)
  • 2 schemas for back-end indexing, processing etc. (the tables are very huge here).

Front and back schemas does not share any foreign key relation between each other. To be highly responsive during the day time, the backend operation run in night time only.

Now the problem is the database server is heavely loaded at night time and often we get timeout errors. I want to spread the backend operations through out the day to overcome this issue with no impact on the front end operations. when i see the performance graphs, during daytime the server and the DB in it is very minimally used.

My knowledge and exp on DB concepts is limited. Following are the options which i think of.

  1. I might not get a approval for 2 sql server machines.
  2. Front schemas in a separate DB on the same sql instance. Place the front DB in separate drive.
  3. Front schemas is separate filegroup. and place the filegroup in saperate drive.

Please let me know the pros and cons of my options and any other options which you think suits here. Thanks in advance.