nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

7.3.1 and databases

Tim__D

If I'm planning on installing LiveSite / SitePublisher in the future but for now am just using TeamSite and OpenDeploy, how many databases should I configure in the install? The documentation is a little vague.

Find more posts tagged with

Comments

Tim__D

If I'm planning on installing LiveSite / SitePublisher in the future but for now am just using TeamSite and OpenDeploy, how many databases should I configure in the install? The documentation is a little vague.

Are there benefits to separate databases if so I'd be interested in whats working for folks.

Thanks!

nipper

If it is anything like 7.2.1 you must have at least 2.

Tim__D

If it is anything like 7.2.1 you must have at least 2.

In my current installation 6.7.2 SP2 I have just one for the EventSubsystem. In 7.2.1 what databases are needed and what are they for?

nipper

Again, speaking for 7.2.1

SP wants one, it will accept the Event subsystem.

Also LSDS wants one and it must be different (different DB, could be the same server) than the others.

Don't have LSDS or SP ?

Too bad, you need them anyway. :mad:

Tim__D

Here is what it says in the doc.

1). In the DBMS, create databases for the following items:
* Common Services
* EventSubSystem
* TeamSite Reporting
* SitePublisher (development environment).

You can have a single database for all the subsystems mentioned above
except ReportCenter.

It goes on to say this....

2). Create databases for the following components items:
* TeamSite
* LiveSite Display Services Runtime. Refer to the Web Solutions Runtime
Components Installation Guide for more information.
* LiveSite Content Services Authoring
* LiveSite Content Services Runtime. Refer to the Web Solutions

Again, speaking for 7.2.1

SP wants one, it will accept the Event subsystem.

Also LSDS wants one and it must be different (different DB, could be the same server) than the others.

Don't have LSDS or SP ?

Too bad, you need them anyway. :mad:

Do you mean to say I should be using those products Smiley Happy

or just that I should not have to set up the databases if I'm not using them?

I guess I'm looking for configurations that work best one db or many? Also..what the difference between the EventSubsystem DB vs the "TeamSite" database is?

nipper

For 7.2.1, even if you have a non-SP license, it still wanted SP and LSDS DBs available.

Again I was able to install 7.2.1 with only 2 disparate DBs, I hope 7.3 behaves the same

date.png

main.png

For 7.2.1, even if you have a non-SP license, it still wanted SP and LSDS DBs available.

Again I was able to install 7.2.1 with only 2 disparate DBs, I hope 7.3 behaves the same

It does Andy...

Tim__D

For 7.2.1, even if you have a non-SP license, it still wanted SP and LSDS DBs available.

Again I was able to install 7.2.1 with only 2 disparate DBs, I hope 7.3 behaves the same

So is this what you have?

Database #1
TeamSite Event Subsystem + Site Publisher

Database #2
LSDS (even though I'm not running it)

Our IT group just finished the install with 1 database which is why I'm asking. The docs are vague and don't recommend cons pros of one or many databases.

nipper

Get a second, or wait while they install it during the middle of the install

I have had to do that before.

dataset.png

parameter.png

error.png

Tim__D

Get a second, or wait while they install it during the middle of the install

I have had to do that before.

In TS 7.3.1 you have to know up front before the install what databases you want to use and for what. So I still have some question about what the best option is.

Is it better to have all the "sub systems"
* Common Services
* EventSubSystem
* SitePublisher (development environment).
in one database or separate databases?

In the documentation is says
"2). Create databases for the following components items:
* TeamSite"

Is the TeamSite database outlined in step #2 different than the database for the subsystems?

nipper

In TS 7.3.1 you have to know up front before the install what databases you want to use and for what. So I still have some question about what the best option is.

Is it better to have all the "sub systems"
* Common Services
* EventSubSystem
* SitePublisher (development environment).
in one database or separate databases?

In the documentation is says
"2). Create databases for the following components items:
* TeamSite"

Is the TeamSite database outlined in step #2 different than the database for the subsystems?

I went with 3. Events (and common services), SP and then LSDS

Could easily have put SP with Events and just called it Teamsite.

Tim__D

I went with 3. Events (and common services), SP and then LSDS

Could easily have put SP with Events and just called it Teamsite.

We're not installing SitePublisher and LiveSite initially. Just TS 7.3.1, OD 7.3.1 and Search 7.3.1.

Sounds like I can run all the common services and events on one database initially then if we install SP, create a SP database or use the existing "TeamSite" database. The if we install LS create the LS database.

Correct?

Snap 2014-04-01 at 12.38.32.png

nipper

It will likely ask for the LSDS DB, whether you are install it or not. So have one ready

Screenshot from 2014-04-01 16:12:13.png

srosewall

It will likely ask for the LSDS DB, whether you are install it or not. So have one ready

You can select "No database" for SitePublisher / LSDS.
That saves you having to create a dummy database for the install.
If you really feel the need to have a database for SP / LSDS, you can add one later...

date.rptdesign

Tim__D

You can select "No database" for SitePublisher / LSDS.
That saves you having to create a dummy database for the install.
If you really feel the need to have a database for SP / LSDS, you can add one later...

Thanks. I just went through the install today again and selected "No database" when it got to the SitePublisher part. Also in the beginning I elected not to install LiveSite Content Services Authoring since I don't have a LiveSite or SitePublisher licence.

FYI - It prompted me for database information regarding both "Reporting" and Administration even though it did not specify Reporting as a component during the install.

compute coulmn.png

output.png

Adam Stoller

Thanks. I just went through the install today again and selected "No database" when it got to the SitePublisher part. Also in the beginning I elected not to install LiveSite Content Services Authoring since I don't have a LiveSite or SitePublisher licence.

FYI - It prompted me for database information regarding both "Reporting" and Administration even though it did not specify Reporting as a component during the install.

There's some confusion in the product (IMO) between "TeamSite Reporting" and "ReportCenter" - I think they're two different things but I couldn't tell you what the first one is - other than something that requires DB setup during the installation.

If you manage to find out more detailed information about this, please post it.

Reji Varghese

Tim,
Even during our install, it was prompting for a database information and what i had was just 1 database for the entire TeamSite and its components install.

So, wherever the installer prompted me for a database, i put in the same DB thin client details and it created different tables in the same database.

I am not sure whats in the DB. But it took like 1.2 GB of space.

Thanks !!!

Thanks. I just went through the install today again and selected "No database" when it got to the SitePublisher part. Also in the beginning I elected not to install LiveSite Content Services Authoring since I don't have a LiveSite or SitePublisher licence.

FYI - It prompted me for database information regarding both "Reporting" and Administration even though it did not specify Reporting as a component during the install.

Garth McMillan

If anyone does find out what best practice for the database set-up in 7.3.1 is, we'd also be interested to know, as the documentation is a little vague.

Currently we're attempting an install/upgrade with 4:

Common services (core TeamSite, event subsystem etc.)
Reporting
LiveSite display services
LiveSite content services

ReggieRWalker

For those interested, this is what I got from Support regarding a 7.3.1 install:

The number of databases that are required are going to depend on what components you are going to use.

Here is the list of databases and the recommended default initial sizes:
Here are the default sizing guidelines for the TS databases:
- Common Services 50MB - This stores information on installed Autonomy products and does not grow or change unless an application is installed or uninstalled.
- Report Center 500MB - This is for Basic Reporting and is also used by the Administration Console.
- SitePublisher 50MB - Only used if you are using SitePublisher.
- LS Display Services 50MB - LiveSite database only used if a DB is selected for SitePublisher.
- lscsauth 50MB - LiveSite Content Services Authoring.

One SQL Server database can be used for Common Services, Report Center, lscsauth, and SitePublisher.
The LS Display Services DB must be separate from the SitePublisher DB, although it can be on the same instance as the SP database.

If you're planning to install Advanced Reporting, then it would be best to put the Report Center database on its own separate DB.

That would result in this configuration:
- One database for Common Services, lscsauth, and SitePublisher.
- One database for Report Center.
- One database for LS Display Services.
Naturally, you could create a separate DB for each component if you wish. And please note that all of these databases can reside on the same DB server in the same instance.