New answers tagged

2

Since you are planning to DROP a column and the indices that support it, I'll assume that doing so is a product of well-thought plan. Also, I'll assume that you want to drop ANY indice that use the to-be-deleted column, regardless of how it is used. If so, you can build your script based upon something like below. You can put this in a stored procedure ...


1

One would hope that the indexes were created for a good reason and not just to annoy other people who would use the database. Assuming these indexes have (or at least had) a good reason to exist, writing a script to blow them away without understanding why they were created or having a plan to replace them seems like a bad idea. Potentially a better ...


1

Transportation is just moving data from one place to another - in ETL, from source system to either staging area, data warehouse or data mart. Transformation is changing data structure so that it meets data warehouse needs - i.e. star schema, denormalization, aggregation, calculations, data cleansing, data enrichment etc. Both happen while ETL, but the ...


0

The .bak file is a Microsoft SQL Server binary backup format. It cannot be used with MySQL - no matter even if you rename it to use another file name extension. A valid .sql file for MySQL is a plain text file with SQL statements supported by MySQL - refer MySQL documentation at http://dev.mysql.com/doc/refman/5.7/en/sql-syntax.html. To migrate data from ...


3

Good luck. You'll need to do way more work than just a "restore". Essentially, you'll need to create a custom pipe to convert the data in the SQL Server database into the table structure used by WordPress. Even if the table structure was identical, and it isn't, you can't "restore" a .bak file into a MySQL database. The .bak does not contain SQL ...


0

Assuming your queries are against regular Access tables, you should be able to replace the Access tables with Linked Tables to your SQL Server. The Linked SQL tables have to have the same names and structure to in order for this to work. I don't have the 2008 version of Access so I can't give exact instructions but look in the menus for something like ...


1

What you are describing is data migration. To do this successfully you need to understand both the old data and new schemas, business rules and the data itself. To migrate the data the most common option is to write conversion scripts which insert data into the new schema that respect the new schemas rules, referential integrity and business logic. If ...


1

Migrating the Data is a Job in itself Keeping Data in sync is a job is yet another job. Creating a new front end is yet another job. there's lots of ways to tackle the problem. there's a lot that can go wrong with data migrations, so if you've never done one before unless the business is yelling for it I'd move very slowly and carefully. 1st I'd ...


0

A possibly simple way is replacing all MS-Access tables with links to views in your SQL Server with the exact same structure as the old Access tables. If the views are simple enough (e.g. a select statement from a single table with a primary key and unmodified columns -other than renaming them-) they'll be directly updatable, otherwise you can use updatable ...



Top 50 recent answers are included