Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Is another sepearate DB liscence recommended

All

Considering implementing Orion SLX. Is it advisable to buy a seperate SQL DB liscence or use the boxed product. Just concerned with some of the feedback that the DB limit of 2Gb may cause operational issues. What is the forums experience?

Jon

Find more posts tagged with

Accepted answers

All comments

mgibson

I have SLX. Yes the 2G limit is easily reached as I experienced this with the ToolKit. May I suggest you use the enterprise Version of the O/S or you will also be limited to 2GB of Memory!

Don331

You will want to use a full license for SQL server. 2GB is easy to reach.

Don Barry
Aegis Mortgage Corp
Houston, TX

pblatz

Jon,

I recommend using a server edition of SQL.
First, you aren't bound by the 2GB limit.
Even if the DB isn't at 2GB, the daily maintenance processes need to be able to grow the tables, if that fails so doed maintenance.
Second, if you already have SQL running, adding another database is handled by the configuration wizard.
Finally, Solarwinds support staff can help you determine the size your database could grow to using some numbers you provide, give them a call.

Thanks,
P. B.

Success requires three bones--wishbone, backbone and funnybone. Kobi Yamada

BwlBoy

Has anyone used SQL 2005 yet? Just a quick question to see if there are any issues before i draw up the Purchase Order?

pblatz

We will be testing SQL-2005 begining in January.

Thanks,
P. B.

Success requires three bones--wishbone, backbone and funnybone. Kobi Yamada

Mithrilhall

I haven't used Orion with SQL 2005 but I have used Cirrus with 2005 with no problems. I've even imported into Cirrus(SQL 2005) from Orion(SQL 2000) without any problems.

CCrew

quote:Originally posted by mgibson

I have SLX. Yes the 2G limit is easily reached as I experienced this with the ToolKit. May I suggest you use the enterprise Version of the O/S or you will also be limited to 2GB of Memory!

I'm curious where you got this number? MSSQL Standard supports more memory than 2gb, albeit with a boot.ini switch. My Orion SQL box has 4gb in it with the switch set to /3gb for SQL. AWE support is in Enterprise which allows you past 4gb, but there's not a 2gb limitation in any version that I'm aware of.. I'd hate to see someone spend the difference between the versions due to incorrect info.

Regards,
Roger