melnikok Absent Member.
Absent Member.
2458 views

Planning for Database Size

I am running Microsoft SQL 2005 on Windows 2003 both are service packed :). I want to build a 2008 server and run SQL 2008 service packed all around for my new 11.1a upgrade from my existing 10.3.3 system. I have a SQL server, 3 primary servers and 6 sat servers right now. I have the potential of 10k devices, 6k bundles and 300 policies by 2013. I want a drive for my 2008 server that will be able to be big enough. I currently have 1260 devices, 4k of bundles and 200 policies.

Can anyone tell me the calculation for determining database size for this type of application.
Labels (2)
Tags (3)
0 Likes
6 Replies
Micro Focus Expert
Micro Focus Expert

Re: Planning for Database Size

ZCM Patch Management and the ZAM Feature to Track Process Usage both can
result in very very large database tables.

Excluding those options which are not in the BASE ZCM product, a rule of
1GB per 1K devices is a good rule of thumb for the Database.

The Transaction log can also grow to a massive size if not maintained.
Properly maintained, generally it should not grow bigger than the DB.

Many Processes can require 2-3 times the Space of the DB (Rebuilds, etc...)

So I would expect about 10GB DB, but I would want at least 30GB for that
size DB for an absolute minimum size.

However, an assumption of a 20GB size would be safer and perhaps 60GB
total space for a recommended size if you are really limited in space.

I would sleep well at night if I knew my DB was allocated 100GB.

If you do go too small, then some of the operations that need swap space
can be run to run the output of those operations to other
drives/locations, but may take a little know how on how to to that.




On 11/22/2011 10:26 AM, melnikok wrote:
>
> I am running Microsoft SQL 2005 on Windows 2003 both are service packed
> :). I want to build a 2008 server and run SQL 2008 service packed all
> around for my new 11.1a upgrade from my existing 10.3.3 system. I have a
> SQL server, 3 primary servers and 6 sat servers right now. I have the
> potential of 10k devices, 6k bundles and 300 policies by 2013. I want a
> drive for my 2008 server that will be able to be big enough. I currently
> have 1260 devices, 4k of bundles and 200 policies.
>
> Can anyone tell me the calculation for determining database size for
> this type of application.
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
melnikok Absent Member.
Absent Member.

Re: Planning for Database Size

OK...I do have PM. So I am wondering what is going on here. I have a 100gb drive and the space used on the drive is 50gb already. It could be the transaction log I suppose or it could be PM. Or it could be my lack of ability to maintain a healthy database. I will look into the maintance part but if you have any suggestions or links I would appreciate it. What would PM be adding to the database size per device? I would like to have the healthiest database I can before upgrading.
0 Likes
melnikok Absent Member.
Absent Member.

Re: Planning for Database Size

Correction!!!! My mdf file is 27gb and my ldf file is 3mb. I am not sure if that helps figure anything out but wanted to correct my crazy claim of a 50gb database.
0 Likes
ukdtom Absent Member.
Absent Member.

Re: Planning for Database Size

Time for a Rebuild IMHO, as well as a cleanout


> http://www.novell.com/support/viewContent.do?externalId=7004256


>

http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=InfoDocument-patchbuilder-readme5081690&sliceId=&docTypeID=DT_SUSESDB_PSDB_1_1&dialogID=186824542&stateId=0%200%20186826456


>

http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7007240&sliceId=1&docTypeID=DT_TID_1_1&dialogID=186824542&stateId=0%200%20186826456


--
Tommy Mikkelsen
IT Quality A/S, Denmark
Novell Support Forums SYSOP / NKP

Sorry, but no support through email
Please join http://www.open-horizons.net


melnikok wrote:

> 27gb


Best Regards Tommy Mikkelsen Denmark Please Report back any success or failure, That way we all learn Sorry, but no support through email "I hate bugs".......Tommy Lee Jones, MIB
0 Likes
spencapl Absent Member.
Absent Member.

Re: Planning for Database Size

Hi

I have 25,000 device zone, with 14 primaries and 240 sat servers. The zone has been live for 4 years and our DB is SQl based and is 120 GB in size. Just to give you a real life example of DB size. We have inventory scans running weekly on our devices. We use patch managment and asset management so collection usage stats. Only bits we don't have on yet are Imaging and ZESM.

Hope that helps

Thanks

Spencer
0 Likes
ukdtom Absent Member.
Absent Member.

Re: Planning for Database Size

Haven't touched that many devices, max. 5000 devices, but with ZPM as
well, the database was about 2 Gb, when proper cleanup was done, as
well as a rebuild. (Before it was 14 Gb)

And yes....this was on *cough* Sybase

Response time from ZCC as well as for the clients was much better after
doing so.


--
Tommy Mikkelsen
IT Quality A/S, Denmark
Novell Support Forums SYSOP / NKP

Sorry, but no support through email
Please join http://www.open-horizons.net


spencapl wrote:

>
> Hi
>
> I have 25,000 device zone, with 14 primaries and 240 sat servers. The
> zone has been live for 4 years and our DB is SQl based and is 120 GB
> in size. Just to give you a real life example of DB size. We have
> inventory scans running weekly on our devices. We use patch managment
> and asset management so collection usage stats. Only bits we don't
> have on yet are Imaging and ZESM.
>
> Hope that helps
>
> Thanks
>
> Spencer


Best Regards Tommy Mikkelsen Denmark Please Report back any success or failure, That way we all learn Sorry, but no support through email "I hate bugs".......Tommy Lee Jones, MIB
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.