Thanks for the reply Simon.
We have database pooling since our databases are read only and we wanted to
take advantage of multithreading. Each database connection had the temp view
defined, but I saw a huge performance drop when it came to queries.
I’m going to try sub-selects for now with the
On 2016/05/27 4:17 AM, Michael Hari wrote:
I have a database that contains 2014,2015 and 2016’s worth of data broken down
by year and quarter. In total, this db was 2.36 GB. Because of a replication
requirement where the DB has to be under 2 GB, I’ve split the DB into 3 smaller
databases by
On 27 May 2016, at 3:17am, Michael Hari wrote:
> I have a database that contains 2014,2015 and 2016’s worth of data broken
> down by year and quarter. In total, this db was 2.36 GB. Because of a
> replication requirement where the DB has to be under 2 GB, I’ve split the DB
> into 3 smaller da
I have a database that contains 2014,2015 and 2016’s worth of data broken down
by year and quarter. In total, this db was 2.36 GB. Because of a replication
requirement where the DB has to be under 2 GB, I’ve split the DB into 3 smaller
databases by year (2014.db,2015.db,2016.db).
I would need t
4 matches
Mail list logo