TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ----------------------------------------------------------------------------
Many thanks to the people who've taken time to reply to me posting - I really appreciate it. Here are some of the responses that I've had so far: 1 ---------------------------------------------- As it is the eventcollector that writes into the database, and you have full support for 5 eventcollectors in one databse ISSED, this should work for 5 sites ? right. As I know that the eventcollector writes his data using an ODBC connection you can easily point the ODBC connection to another instance, copy of the database schema. In this case you end up with 2 databasefiles and 2 seperate reports, maybe what you want to achieve. The support of 5 EC into one single database is mainly because the database will be the bottleneck at that point. Hope this can help you already on the way. > This is what I had in mind, although I'm a little unsure about the ISS installation >scripts and whether the configuration would be supported by ISS (eg do they hardcode >"ISSED" anywhere?!) 2 ---------------------------------------------- I am not 100% sure if it will help but I would look at the ODBC setup in the ECs. This is where you might want to adjust it and direct the logs to different SQL instances. > Yup, my thoughts too. 3 ---------------------------------------------- Here is the how to from the ISS Knowledge base. The products are not important because they all use the same DB name in SQL. From this you should get an idea of what needs to be done. The asset DB and the Event Collector can be kept on a locale system to that separate instance of IDS. The Enterprise DB hardware can be used by all the instances of RealSecure, all you would need to do is rename the DB within SQL. Hope this helps, and feel free to shoot questions my way if you like. (Reference 010709-000004) > This looked very interesting, thanks Paul. It talks about RealSecure and Safesuite >database name conflicts, and how to detach them and re-attach them under other names. >It *DOESN'T* mention tweaking ODBC definitions so I'm a little puzzled on that >account. Perhaps it assumes that users will know to do that? I don't know... 4 ---------------------------------------------- I believe this can be done provided you are using different event collectors to write to your databases. However I have not tested this with databases using different names. You have to create a standard ISSED derived from the one created during install, give it a different name and then attach the database using SQL commands to make this work. In the past you had to use Crystal Info Reporter to change the ODBC connect for the builtin reports, I dont know if that problem still exists. WGM 6.5 console does support connections to different sql databases, one at a time, I would give it a try. > If people are doing this i'm be happier, and if ISS support it I'll be very happy. >It sounds like it may need some tweaks at install (ie deriving it from the standard). 5 ---------------------------------------------- A gentleman from ISS is also looking into it for me... >>> I'm pretty sure you can change the database, and any ODBC connections, but I'd prefer it to be a "supported configuration" by ISS - not just something we could try at our own risk. Having said that, if it looks straightfoward and other people are successfully doing it, we could take the plunge anyway. I've had a play with the WGM install script but it seems to do a lot under the covers. Okay, it asked me where the database was when I installed the console component (and i don't know whether it wanted the server's address, or some kind of ODBC alias - i'm not an expert), but as far as I remember it didn't ask me any questions when I selected installation of the Enterprise Database and Asset components. I first tried installing those on the console, thinking it was required for the console to set up the database remotely, then decided they had to be run on the database server itself... but when I ran them on the database server itself I don't think it asked me anything (such as "which named instance do you want" or "which drive do you want to use"?). Then again, I'm not a SQL expert. Jason
