Auto export database/tables from Local Sql Server to Azure.

Tagged: 

This topic contains 3 replies, has 2 voices, and was last updated by Profile photo of Don Jones Don Jones 2 years, 3 months ago.

  • Author
    Posts
  • #18258
    Profile photo of Mat Amos
    Mat Amos
    Participant

    Hi,

    I'm new to powershell and currently we use a c# app on the local to export data from local to our azure db. I now want to explore other options for auto exporting
    and have pegged looking at powershell for a while, after some initail investigations I have to admit I was surprised how much there was too it but I haven't been succesful in
    tracking down specific'ish info or scripts on my requirement.

    So I'm looking for some advice/pointers/scripts – anything that might help basically 🙂

    Some of our clients run sql server 2005 and some 2008 (express editions). If need be we can probably upgrade the 2005 although I've noted 2005 can run powershell with some install's applied.

    So my requirement really is the auto export of preferably just some tables but maybe the whole database from a local sql server/db to an azure sql server/db using powershell.

    thanks,

  • #18262
    Profile photo of Don Jones
    Don Jones
    Keymaster

    I'm actually not sure I'd peg PowerShell for SQL-to-SQL data transfers. Honestly, it's not going to be the best performance. I'd probably lean toward something in C# myself, or an SSIS package. PowerShell might kick that off, sure, but I think you'll get far better performance and reliability that way. I think most experienced SQL folks would aim for SSIS also.

  • #18265
    Profile photo of Mat Amos
    Mat Amos
    Participant

    Thanks Don,

    I would agree but all our clients only have the express editions of sql server which I think doesn't include ssis.

  • #18267
    Profile photo of Don Jones
    Don Jones
    Keymaster

    Express with Advanced Services does. Also, you can install Express w/AS on an intermediate machine to run packages on, if needed. End of the day... this isn't a task I'd personally do in a PowerShell script. It isn't the right tool for the job.

You must be logged in to reply to this topic.