Tag Info

New answers tagged

4

Do a back-up/ restore - takes longer but appears to be a favoured method. This is what we prefer. -- Backup and Restore. Safer Method. Option to detach the database using sp_detach_db and then attach it using CREATE DATABASE ... FOR ATTACH; or detach and attach using the GUI will actually detach the database from the source server. Many things can ...


2

The backup/restore method is generally my preferred way especially if you're on 2008R2 or higher due to backup compression. If you don't have access to that feature, the backup file generally is still a smaller file copy than the .mdf/.ldf file copy because a backup file removes any wasted space in those database files


3

You can update 6.5 to 2000, from 2000 to 2008 and from there go to 2012 but its much better to script out the schema and bcp the data as Kin suggests. As he seems to be to humble to link to his own post I'll do it for him: Restore SQL Server 2012 backup to a SQL Server 2008 database?


0

Replace the comma with a dot, which is the default "decimal point". ALTER TABLE lca_test ALTER COLUMN prevailing_wage TYPE numeric(10,0) USING translate(prevailing_wage, ',', '.')::numeric; But as long as you are not going to store fractional digits (numeric(10,0)), you should really use integer (covers -2147483648 to +2147483647 or bigint (covers ...


4

I'm ignorant of postgres SQL syntax, however this appears to be an issue with either the TYPE numeric(10,0) not containing decimal granularity (numeric(10,2)) would work, or the fact that the currency is in a european format that utilizes commas instead of decimals.


4

There are two very detailled documents here and here. There is a step by step guide (with videos) here. It is no coincidence that two of these documents are from Oracle themselves, it being very much in their interest to get clients to move from SQL Server to their product. Your question is a bit too vague and general for this forum, but since you're new to ...


7

since you are using SQL Server 2008 Web edition, your best bet is to use LOG SHIPPING. Your database size is 100GB, so initializing the secondary from a backup should be considered. Dont use GUI to set up initial logshipping. SO your steps should be : Backup 2008 Web edition database and restore it on 2012 enterprise WITH NORECOVERY. Launch Logshipping ...


1

The 'mysql' database contains users/privileges/passwords. So take the dump of mysql database along with other databases mysqldump [options] --all-databases > all_databases_dump.sql mysqldump -u root -p mysql user > user_table_dump.sql These mysql database tables contain grant information user: User accounts, global privileges, and other ...


0

First I agree you should not migrate from 2000 to 2012 directly. I think that process has been covered well. I wanted to suggest you find out for sure if anyone is using the databases and what they are using them for. It may be that they are not being used. It happens and if that is the case then you have no worries. It might be that adding 2 or 3 tables and ...


1

Nothing bad happened even if you took the config server offline during a chunk migration. In order for a chunk to be marked as migrated, all three config servers need to be up (Contrary to popular belief they do not form a replica set.). (The following is a tiny bit simplified for the sake of shortness.) When a chunk is moved, a global (read cluster wide) ...


0

You say you "have come across three old databases sitting on SQL Server 2000" which leads me to believe you only need the data. I would guess that if they were being run for a purpose, you would know. If this is the case, ignore all questions of users, security, etc. Import/Export wizard all the tables Script the stored procedures and views Check for ...


0

You can not migrate directly from SQL Server 2000 to SQL Server 2012, and if you try to do it you will get the following error number 3169, that is related to compatibility issues. The migration to SQL Server 2012 can be done from one of the following versions (minimum versions) SQL Server 2005 SP4 or SQL Server 2008 SP2 or SQL Server 2008 R2 SP1. So ...


6

Stating there is no workaround seems a little premature. You say your database only contains a few tables and views. Why not export the tables and views schema as SQL create statements and run them on your target database? You could then also export the actual data into something like CSV format and import them into the target database, or perhaps even ...


17

No, there is no workaround to upgrading a database directly from 2000 to 2012. Since you don't have a ton of data, you can do all kinds of things to move the data (but not the database as a whole), including: Import/Export wizard SSIS BCP Manual queries using a linked server from 2012 or an application However these will not necessarily bring over other ...


2

No, you cannot migrate it directly from 2000 to 2012. What you can do is install a temporary instance of 2005 OR 2008 oR 2008R2, restore the 2000 database here. Once done you can now upgrade from installed instance by taking the backup of database from that instance and restoring onto sql server 2012. You will have to make the migration in two steps: ...



Top 50 recent answers are included