• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 265
  • Last Modified:

How much info is it practical to keep within a single *.mdf file?

I'm using SQL Server 2008 Workgroup w/ Microsoft Access to run an internal company database. I have about 100 users with no more than 50 on at any one time.

I'm going to be integrating their collection of scanned documents (about 16GB) into the database and I'd expect that to grow to 100GB+ over the next few years. I'm curious... although Microsoft says workgroup can have unlimited database size are there any concerns with having 100GB+ in one mdf?

I can't use filestream at this point because from what I've seen it requires Windows Authentication which would be complicated for me to implement due to most of the company being linux based and my app would require an overhaul to make it work.

So, considering how light the usage is on this server (no more than 50 active users) does storing all this content inside the database seem viable from a performance/stability perspective?

Any input would be appreciated.
0
DailyDilemma
Asked:
DailyDilemma
1 Solution
 
RiteshShahCommented:
well, as you know your workgroup edition supports unlimited database size and that is true but the way you are going to grow with your database, I recommend you to create more filegroups and split your database into few more file group to decrease IO load.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now