Novice help with Solomon

  • I'm a general management type, not a network/db expert and could use a little help. We're just installing Solomon with SQL Server in a small company (<5 users) and we're thinking about using the same SQL server for another VB application as well (<10 users). It seems to me that we should be able to run both applications on the one server (P4 2.0) but is there anything I'm missing or should watch out for?

  • The big things are stability of application as if one causes sql side issues it can stall the whole server and thus affect your other app. Other than that it is resources themselves and how they are used which can be an issue, DB grows fast, lot's of transactions and TL fills drive. Most of the later can be planned around.

  • Let me give a different perspective -- a non-technical one -- find out what your support people will say. In many shops, Solomon is going to be supported by a vendor of some sort. A very common problem (not necessarily in Solomon but any 3rd party support) is that the first time you have a problem, you're going to be told "we always recommend you be running in X configuration, and you are not - that might be the problem, call us back when you are configured as we recommended".

    I'm fighting that now with a transportation product -- they wanted THREE different systems (database, app server, terminal server server) despite us being a tiny configuration. But they have this "standard" configuration whether you are 5 users or 5000, and if you don't match they don't support you (or at least not well).

    We have Solomon, and so far it's been a well behaved application that I would expect to run just fine with some other application as well. But do make sure that your support channels are not going to give you a lot more grief than the cost of another small server.

    Incidentally, with MSDE free, the cost of another server (or desktop) might be pretty cheap.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply