Extra column when migrating Sybase databases to single SQL Server databaseSet default value for all columns...

Should I file my taxes? No income, unemployed, but paid 2k in student loan interest

Too soon for a plot twist?

Rationale to prefer local variables over instance variables?

Ultrafilters as a double dual

Tabular environment - text vertically positions itself by bottom of tikz picture in adjacent cell

Is "cogitate" used appropriately in "I cogitate that success relies on hard work"?

Was it really inappropriate to write a pull request for the company I interviewed with?

An Undercover Army

How spaceships determine each other's mass in space?

Is there a logarithm base for which the logarithm becomes an identity function?

Short story about cities being connected by a conveyor belt

Unfamiliar notation in Diabelli's "Duet in D" for piano

Paper published similar to PhD thesis

What is the purpose of a disclaimer like "this is not legal advice"?

Tool for measuring readability of English text

Having the player face themselves after the mid-game

A running toilet that stops itself

After Brexit, will the EU recognize British passports that are valid for more than ten years?

Book where society has been split into 2 with a wall down the middle where one side embraced high tech whereas other side were totally against tech

Did Amazon pay $0 in taxes last year?

What does it take to become a wilderness skills guide as a business?

How does a sound wave propagate?

Why would /etc/passwd be used every time someone executes `ls -l` command?

I am the light that shines in the dark



Extra column when migrating Sybase databases to single SQL Server database


Set default value for all columns with specific name within a databaseMigrating SQL database to a new SQL serverDon't delete exist data with SSMAOptions to migrate large database from Sybase ASE to SQL Server with minimum downtimeWhy SQL Server Migration Assistant keeps crashing on the 'Migrate Data' step?TEXT data migrate from Sybase to SQL ServerMicrosoft access to Sql Server Data MigrationSample Sybase ASE 15.0.3 databaseMigrating Access 97 to Sql Server - Version ErrorMigrating 300GB database to Azure SQL ServerMigrate on-premise SQL Server databases to Azure SQL Database













0















I'm trying to use Microsoft's SQL Server Migration Assistant for Sybase ('SSMA') to migrate multiple Sybase databases (that have the same schema) to a single SQL Server database.



All of the tables in the new SQL Server database will have an extra column project_id, which should have a fixed value depending on which Sybase database data is being migrated from.



I've migrated the schema using SSMA, and then created the new columns in SSMS. But I the new columns aren't visible in SSMA, and I can't see any way to achieve what I want to do.



How can I migrate data from each of the Sybase databases whilst utilising the extra project_id column?










share|improve this question
















bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    I'm trying to use Microsoft's SQL Server Migration Assistant for Sybase ('SSMA') to migrate multiple Sybase databases (that have the same schema) to a single SQL Server database.



    All of the tables in the new SQL Server database will have an extra column project_id, which should have a fixed value depending on which Sybase database data is being migrated from.



    I've migrated the schema using SSMA, and then created the new columns in SSMS. But I the new columns aren't visible in SSMA, and I can't see any way to achieve what I want to do.



    How can I migrate data from each of the Sybase databases whilst utilising the extra project_id column?










    share|improve this question
















    bumped to the homepage by Community 10 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      I'm trying to use Microsoft's SQL Server Migration Assistant for Sybase ('SSMA') to migrate multiple Sybase databases (that have the same schema) to a single SQL Server database.



      All of the tables in the new SQL Server database will have an extra column project_id, which should have a fixed value depending on which Sybase database data is being migrated from.



      I've migrated the schema using SSMA, and then created the new columns in SSMS. But I the new columns aren't visible in SSMA, and I can't see any way to achieve what I want to do.



      How can I migrate data from each of the Sybase databases whilst utilising the extra project_id column?










      share|improve this question
















      I'm trying to use Microsoft's SQL Server Migration Assistant for Sybase ('SSMA') to migrate multiple Sybase databases (that have the same schema) to a single SQL Server database.



      All of the tables in the new SQL Server database will have an extra column project_id, which should have a fixed value depending on which Sybase database data is being migrated from.



      I've migrated the schema using SSMA, and then created the new columns in SSMS. But I the new columns aren't visible in SSMA, and I can't see any way to achieve what I want to do.



      How can I migrate data from each of the Sybase databases whilst utilising the extra project_id column?







      sql-server migration sybase ssma






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Aug 7 '14 at 10:16









      marc_s

      7,12053849




      7,12053849










      asked Aug 6 '14 at 9:14









      CocowallaCocowalla

      11819




      11819





      bumped to the homepage by Community 10 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 10 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Turns out SSMA just ignores any extra columns you create after migrating the schema - so I could set the default for the project_id columns before migrating data from each Sybase database and have them populated with those defaults.






          share|improve this answer

























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "182"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f73268%2fextra-column-when-migrating-sybase-databases-to-single-sql-server-database%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Turns out SSMA just ignores any extra columns you create after migrating the schema - so I could set the default for the project_id columns before migrating data from each Sybase database and have them populated with those defaults.






            share|improve this answer






























              0














              Turns out SSMA just ignores any extra columns you create after migrating the schema - so I could set the default for the project_id columns before migrating data from each Sybase database and have them populated with those defaults.






              share|improve this answer




























                0












                0








                0







                Turns out SSMA just ignores any extra columns you create after migrating the schema - so I could set the default for the project_id columns before migrating data from each Sybase database and have them populated with those defaults.






                share|improve this answer















                Turns out SSMA just ignores any extra columns you create after migrating the schema - so I could set the default for the project_id columns before migrating data from each Sybase database and have them populated with those defaults.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Apr 13 '17 at 12:42









                Community

                1




                1










                answered Aug 7 '14 at 9:58









                CocowallaCocowalla

                11819




                11819






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Database Administrators Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f73268%2fextra-column-when-migrating-sybase-databases-to-single-sql-server-database%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    ORA-01691 (unable to extend lob segment) even though my tablespace has AUTOEXTEND onORA-01692: unable to...

                    Always On Availability groups resolving state after failover - Remote harden of transaction...

                    Circunscripción electoral de Guipúzcoa Referencias Menú de navegaciónLas claves del sistema electoral en...