
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2012 12:30 PM
Hi Lansweeper Support,
At Rontec we already have a paid license for one AD environment, and we would now like to test it on another non AD environment. We would purchase another individual license to achieve this after test. We would however like to use the same SQL Server to record the data to, but not the same database, as we are using it for the live registered database.
Can you confirm this is possible, as I cannot see a way of pointing the SQL Server to a different database, via the install, and if so how to do it ?
Thanks for your help.
Regards,
Mike.
At Rontec we already have a paid license for one AD environment, and we would now like to test it on another non AD environment. We would purchase another individual license to achieve this after test. We would however like to use the same SQL Server to record the data to, but not the same database, as we are using it for the live registered database.
Can you confirm this is possible, as I cannot see a way of pointing the SQL Server to a different database, via the install, and if so how to do it ?
Thanks for your help.
Regards,
Mike.
Labels:
- Labels:
-
Archive
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2012 03:29 PM
What we are saying is that, while it is technically possible to change your Lansweeper database name to something else, we do not support doing this. This setup will inevitably cause problems. So you should not install two Lansweeper databases on one SQL Server.
An ideal solution would be to host your second database on another machine. (An Enterprise license would not help. With an Enterprise license, multiple scanning servers report back to a single database.)
An ideal solution would be to host your second database on another machine. (An Enterprise license would not help. With an Enterprise license, multiple scanning servers report back to a single database.)

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2012 03:14 PM
Hi Support,
So you cannot have more than 1 lansweeper database on one SQL server then ?
Or can I interpret your reply to mean you would allow the second install to connect to the same database, but only with Enterprise licensing ?
As we are only testing in our non AD environment, and more importantly, we do not want the information gathered mixed together, is there no other work around ?
Thanks for your help.
Regards,
Mike.
So you cannot have more than 1 lansweeper database on one SQL server then ?
Or can I interpret your reply to mean you would allow the second install to connect to the same database, but only with Enterprise licensing ?
As we are only testing in our non AD environment, and more importantly, we do not want the information gathered mixed together, is there no other work around ?
Thanks for your help.
Regards,
Mike.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2012 02:28 PM
Technically, you could rename the database. We do not support this however and strongly advise against it. The installer looks for the "lansweeperdb" database during upgrades. Renaming the database will therefore inevitably cause problems.
