Tag Info

New answers tagged

2

The solution is very simple. If you do UPDATE exchange SET emp_id = {some expression here on the params column}; -- no WHERE clause! it will do exactly what you want: pick the params from the row to be updated, calculate the expression and update emp_id with its value. As there is no WHERE clause, it will go through the whole table. You don't need the ...


2

Since you're staying with 2008R2 (both source and destination) there is nothing stopping you from just backing up and restoring all of your databases including the system databases. As Shanky pointed out, this would save a great deal of time: 1) Backup and Restore Databases - Is this the best option? It's an option. If you need the downtime to be less, you ...


0

The fastest way would be to create a cluster an join your current stand alone server to the cluster as a new node. Set the database to full recovery model, take a full backup and a transaction log backup and restore them to the instance on the other node with norecovery. If you have a good full backup (most recent), it would be possible to set the recovery ...


1

Pentaho have an open-source tool called Kettle that we use for ETL development with Postgres. It is quite good and very comprehensive. http://community.pentaho.com/projects/data-integration/


1

First of all: Why the heck would you move data FROM SQL Server TO Postgres in order to use SQL to manipulate it? Do you realise that Postgres does not have a parallel query executor while SQL Server has? This means that even on a tiny server, a data warehouse data manipulation query will run several times faster on SQL Server than it does on Postgres . There ...


5

That is not a supported upgrade path. how would you recommend I proceed? My recommendation would be to install side-by-side and then migrate (backup and restore) your databases to the SQL Server 2014 instance.



Top 50 recent answers are included