Forum Replies Created

Viewing 15 posts - 31 through 45 (of 472 total)

  • Reply To: Azure DevOps and branches

    Steps taken so far:-

    Create brand new database RG_Test

    Create new project in Azure (also called RG_Test)

    Use Git Bash to clone project repository (Azure) to local repository

    Connect RG_Test to local repository and...

  • Reply To: Azure DevOps and branches

    Hi Grant

     

    As far as I know, there are no constraints on any table in this database.

    I'll create a new database (so it's just a shell) and retry.

     

    Regards

     

    Richard

  • Reply To: Azure DevOps and branches

    Hi @Grant

    Thanks for that and that seems fine.

    In this case, I'm making changes to two different objects when I encountered the conflicts.

     

    Richard

  • Reply To: Azure DevOps and branches

    That makes two of us.

    Forgot to mention, I'm using SQL Source Control (from RedGate) to do the Commit/Push) so I'll have a look through the settings and see if I've...

  • Reply To: Azure DevOps and branches

    It's entirely possible that I could have two projects affecting the same database (not just the same object).  The would have two different timeframes but could be worked on simultaneously...

  • Reply To: Azure DevOps and branches

    Hi @michael-2   Apart from the Release branch, that's what we're trying to do.

    The problem is, we might need to make multiple changes to the same database under different projects.

    E.g. I...

  • Reply To: Using a trigger to create schemas

    Thanks all

    @jeff - That would be nice but we don't have a reporting database as such.  Users can connect directly to the main database through all sorts of mechanisms (SSRS,...

  • Reply To: Using a trigger to create schemas

    Hi @Ed - I did think about that which is why I put in the TRY/CATCH blocks.  No matter what I put in for @SchemaName, the trigger fails (so the...

    • This reply was modified 3 years, 3 months ago by richardmgreen1. Reason: Typo
    • This reply was modified 3 years, 3 months ago by richardmgreen1.
  • Reply To: The Broken UDF

    Thanks for that.

    In Chrome, I don't get the "Msg 195, Level 15, State 10, Line 11 'AddOne' is not a recognized built-in function name." bit.

     

    Regards

     

    Richard

  • Reply To: The Broken UDF

    Hi Steve

     

    Just had a look at todays question and it appears the error message is missing so you can't try to pick the correct answer.

    Am I missing something?

     

    Regards

     

    Richard

  • Reply To: Spawning multiple copies of the same SSIS Package

    In reverse order .....

     

    The table it bombed on is only 93k records or so (so not massive).

    It's an external table in an Azure database and looks like this:-

    CREATE EXTERNAL TABLE...

  • Reply To: Spawning multiple copies of the same SSIS Package

    @Phil - that's helped.  VS is now only using around 800MB max.  I'm still getting memory errors.  An example would be:-

    Loading table: Data_Dictionary.Hepatitis_C_Infection_Indicator_SCD; Error Message: Error 0x80070008 while executing package...

  • Reply To: Spawning multiple copies of the same SSIS Package

    Thanks Phil

     

    I'll give that a go and let you know how I get on.

     

    I've also got a timeout error on a fairly large table (90k rows) that I'm looking into...

  • Reply To: Spawning multiple copies of the same SSIS Package

    Hi Phil

     

    Thanks for the link, looks like the memory leak is still there.  Not sure how I'm going to resolve that one with a script task, but I'll do some...

  • Reply To: Spawning multiple copies of the same SSIS Package

    Hi Phil

     

    Each of the 8 GetNextTable packages spawns it's own copy of FDSyncData_Source2Dest using an execute package task.

    It looks like I can get to around 1000 of the FDSyncData_Source2Dest  packages...

    • This reply was modified 3 years, 11 months ago by richardmgreen1. Reason: Typos

Viewing 15 posts - 31 through 45 (of 472 total)