Tag Info

New answers tagged

2

You have a lot of reading and testing to do. There isn't a magic bullet per say but lots of ways of hitting this issue. Firstly setup the 2nd environment as if it were prod, but restore the databases in a test environment and restore the SSIS packages. If reporting services are not dependent on this then focus on this part first. Give your SSIS package ...


0

You didn't mention how the data comes in, but I would hazard a guess that it is through flat files. If this is the case, I worked at an order processing company that used Oracle for the back-end of the WMS we used. We regularly received 10 of millions of records a day. We used SQL loader scripts to load the data. The caveat to that is that the data needs to ...


0

You managed to dump it? Using what? Perhaps a 3.23 version of mysqldump? If so, that is a text file that contains CREATEs and INSERTs. There is at least one incompatibility that it may have: TYPE=MyISAM -- In some version, TYPE was replaced by ENGINE. You say "can't get it into 4.0" -- Does that mean you have a 4.0 and the load fails? With what error? ...


0

In SQL 2008 you're looking for minimum downtime vs no downtime in these cases unless you're willing to shell out a lot of money/time for a few seconds. This sounds like hopefully it's not too complex of an environment so you have several options. How about SQL Mirroring? If your data isn't coming in too fast, it'll sync up and you can 'failover mirror' ...


0

Couple of options: Adding a third node might be possible but as you are running on SQL 2008 you have to figure out a way to replicate the storage between the two locations (https://msdn.microsoft.com/en-us/library/ff878716.aspx) In most cases this would be done with SAN replication. If you can do that you're good to go. If SAN replication is not an option ...


1

Another approach which should work for you is to install PostgreSQL from the PostgreSQL Global Development Group's APT repository. They provide compiled versions of PostgreSQL for all supported versions of PostgreSQL and all supported versions of Ubuntu (and of course some versions of Debian). https://wiki.postgresql.org/wiki/Apt is the starting point for ...


3

@a_horse_with_no_name is quite right. Because you compiled PostgreSQL from source, the usual tools provided by pg_wrapper like pg_ctlcluster and pg_lsclusters are not available. As a result the PostgreSQL init scripts on Ubuntu won't start your PostgreSQL 9.1 DB. You could hook your custom binaries into pg_wrapper, but it's not worth the hassle for a ...


0

pg_basebackup is not the right approach. It won't work, because the 32-bit and 64-bit data directories are not compatible. You will have to dump and reload using pg_dump and pg_restore, plus a pg_dumpall --globals-only restored via psql for user accounts etc.



Top 50 recent answers are included