RE: [SA-list] Future Product Feature

[Norman Crooks]

Title: Future Product Feature

Not sure what serious $$$ means, but sure I'm in.  Provided it includes a migration tool :)

 

Norm Crooks
Moontaxi Media Inc.
260 King Street East, Suite B100
Toronto, ON, M5A 4L5
phn: 416.367.0332
fax: 416.367.3324
www: http://www.moontaximedia.com

 

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael D. Shook
Sent: Tuesday, May 17, 2005 12:35 PM
To: salive@woodstone.nu
Subject: RE: [SA-list] Future Product Feature

OK, I can't resist...

 

How many people would be willing to part with serious $$$ to have a version of SA that has NO (ZERO, NONE) of it's configuration or check data stored locally, but rather all stored in a SQL database (MSSQL, MySQL, etc....) with the checks read from the database every cycle? This would allow seperating the check processing from the check setup, giving people the option of changing without stopping.

 

I know my company would be willing to spend $$$ if we could have a truly Enterprise level version. We're having to look at competitors products because of the more advanced reporting of the checks, teams, on-call, alerting that are not available in SA v5. Also, the lack of ability to have the configuration on a highly available SQL Server is starting to be more and more of an issue.

 

Michael D. Shook
Technical Analyst
[EMAIL PROTECTED]
863 668 4477 (work)
863 860 4070 (cell)
863 665 1261 (fax)
www.saddlecrk.com

 

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx
Sent: Tuesday, May 17, 2005 9:07 AM
To: salive@woodstone.nu
Subject: RE: [SA-list] Future Product Feature

Well that's just an almost complete rewrite :-(

 

Dirk.

 

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vogl, Tom
Sent: Tuesday, May 17, 2005 3:30 PM
To: salive@woodstone.nu
Subject: [SA-list] Future Product Feature

Dirk,

We have had lots of discussion about SA here, and overall we love the product.  If we could ask for only one feature in future releases it would be this:

The separation of the SA check engine from the interface.  This way the engine could be started as a service and never touched while remote connections via Terminal Server, Citrix or whatever could load the interface for adds/changes to the config.

The interface could be compiled or web; based-doesn't matter.  But the current remote access issues make running in service mode challenging to work with SA in a "dark" or remote computer room. 

    Ie:  Remote connect to machine.  Stop SA Service.  Start new desktop copy.  Make Changes.  Save file.  Exit local copy.  Start SA service.

-Tom