v7 Upgrade Top Tip

We upgraded to 7.0.0010 in mid-2011 from 6.2.0030. Generally speaking everything has been behaving as it should but in November, the publish started to hiccup for no apparent reason.

This was very quickly traced to our not having enough database connections configured – we were told that we’ve had the same number configured almost since we installed T4 back in 2004 but that v7 needs significantly more.

We increased from 20 to 200 and all is well once again.

The top tip? Make sure T4 / your infrastructure support people check the number of database connections allocated is appropriate for your install.

This entry was posted in SiteManager. Bookmark the permalink.

One Response to v7 Upgrade Top Tip

  1. Interesting, we had a similar issue but with Site Manager 6.2.0033. We’ve had a database connection pool of about 20 since we installed in late 2006. We moved the timing of a handful of RSS feeds back by one minute and all of a sudden our site started publishing out with no content. The issue was traced to Site Manager running out of database connections.

    We’ve now increased this to 200. And then last week SM started complaining that it had used up those too and was thirsty for more.

    The investigations continue…

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s