Anonymous_User Absent Member.
Absent Member.
1263 views

database considerations for new management zone

I'm building a new SLES/ZCM11 server to support ~1600 devices and from
posts here, I'm a little concerned about performance/maintenance
overhead with either the embedded/remote Sybase database options
(published device limits of 1000/1500 respectively).

I see that SP1 will give us Sybase 12 but no word re: improvements to
max devices and related performance.

I'm leaning towards using MSSQL out of the gates for this zone with the
thought that it (should) avoid 1) any performance pitfalls given the
number of devices and 2) potential hassle of trying to migrate the
database down the road.

Thoughts?

Jeff.
Labels (2)
0 Likes
2 Replies
Micro Focus Expert
Micro Focus Expert

Re: database considerations for new management zone

If MS_SQL works in regards to license/know_how, that would be a great
choice.

Novell is working on numbers for the New Sybase, but they are not released.

There are many issues that can impact performance.
Sybase can handle 1600 devices now without an issue for most Zones.

Issues start coming in when.......
Virtualized and the Performance of the Virtual Server is far below
Physical.

Patch and specific ZAM features can place heavy loads on the DB.
(Imagine Some Optional Configuration Options building Tables 10x the
Size of the entire DB, that could be disabled and still use Patch and ZAM)

Legit Physical Hardware, monitoring your tables for excessive growth,
and occassional rebuilds to keep the indexes looking good should let the
current Sybase do fine. The next should be better.

However, MS_SQL will undoubtedly provide a very strong backend DB.
If you have MS_SQL, go for it.

But I would not think you would be required to go purchase and deploy
it, just for ZCM.



On 4/29/2011 10:51 AM, _jd_ wrote:
> I'm building a new SLES/ZCM11 server to support ~1600 devices and from
> posts here, I'm a little concerned about performance/maintenance
> overhead with either the embedded/remote Sybase database options
> (published device limits of 1000/1500 respectively).
>
> I see that SP1 will give us Sybase 12 but no word re: improvements to
> max devices and related performance.
>
> I'm leaning towards using MSSQL out of the gates for this zone with the
> thought that it (should) avoid 1) any performance pitfalls given the
> number of devices and 2) potential hassle of trying to migrate the
> database down the road.
>
> Thoughts?
>
> Jeff.



--
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
Anonymous_User Absent Member.
Absent Member.

Re: database considerations for new management zone

MS SQL licensing/know-how we can handle.

When you say Sybase 10 should be fine for 1600 devices, does that go for
embedded as well?

I had a discussion this morning and physical hardware is limited -- we'd
likely have to consolidate on a single box (single quad xeon @ 1.86GHz
w/ 8 GB) which means running ZCM on Windows instead of SLES if we want
to go with MS SQL. And consolidation brings up the question of having
the (MS SQL) db back on the same box.

Patching and ZAM will be excluded in the short term. The immediate use
will be policies, imaging and software distribution (bundles) along with
improved support for Win7 in our environment.

Would be nice to see those numbers re: Sybase 12. 😉

J.

On 29/04/2011 12:30 PM, craig wilson wrote:
> If MS_SQL works in regards to license/know_how, that would be a great
> choice.
>
> Novell is working on numbers for the New Sybase, but they are not released.
>
> There are many issues that can impact performance.
> Sybase can handle 1600 devices now without an issue for most Zones.
>
> Issues start coming in when.......
> Virtualized and the Performance of the Virtual Server is far below
> Physical.
>
> Patch and specific ZAM features can place heavy loads on the DB.
> (Imagine Some Optional Configuration Options building Tables 10x the
> Size of the entire DB, that could be disabled and still use Patch and ZAM)
>
> Legit Physical Hardware, monitoring your tables for excessive growth,
> and occassional rebuilds to keep the indexes looking good should let the
> current Sybase do fine. The next should be better.
>
> However, MS_SQL will undoubtedly provide a very strong backend DB.
> If you have MS_SQL, go for it.
>
> But I would not think you would be required to go purchase and deploy
> it, just for ZCM.
>
>
>
> On 4/29/2011 10:51 AM, _jd_ wrote:
>> I'm building a new SLES/ZCM11 server to support ~1600 devices and from
>> posts here, I'm a little concerned about performance/maintenance
>> overhead with either the embedded/remote Sybase database options
>> (published device limits of 1000/1500 respectively).
>>
>> I see that SP1 will give us Sybase 12 but no word re: improvements to
>> max devices and related performance.
>>
>> I'm leaning towards using MSSQL out of the gates for this zone with the
>> thought that it (should) avoid 1) any performance pitfalls given the
>> number of devices and 2) potential hassle of trying to migrate the
>> database down the road.
>>
>> Thoughts?
>>
>> Jeff.

>
>


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.