User profile for Kendra_Little

I just raised a question with the folks over in the dev team to see if this is something that may have changed between your version (is it 3.0.1?) and the current 3.0.4 version. They are over in Cambridge so I may not hear back right away, but sometimes they appear when I least expect them! / comments

I just raised a question with the folks over in the dev team to see if this is something that may have changed between your version (is it 3.0.1?) and the current 3.0.4 version. They are over in Ca...

0 votes

Hi there, Interesting question! I did a few tests: I created a table named dbo.duplicate, and a table type named duplicate. Committed, ran sequence of build and deploy via powershell, they succeeded. Added a procedure, dbo.useduplicate, taking a parameter of the duplicate type as a TVP, and also using the type inline in the procedure in a writable way. Committed. Build and deploy still succeeding. Added a trigger onto the dbo.duplicate table, committed. Build and deploy still succeeded. The SQL I used is here. So something about our scenarios is different -- if you check out the SQL I'm using, any suggestion on what changes need to be made to reproduce your setup? I may just have misunderstood what you are describing. Thanks! Kendra / comments

Hi there,Interesting question! I did a few tests:I created a table named dbo.duplicate, and a table type named duplicate. Committed, ran sequence of build and deploy via powershell, they succeeded....

0 votes

That makes sense, thank you for clarifying, @PeterDaniels ! Coincidentally, I met with members of the SCA team just this morning to chat about clarifying concepts around baselining in our docs. One of my questions was, "are there times when we do NOT want to create a baseline, and what are those exceptions?" The list of exceptions I have as of this moment is: New project / greenfield development, when there is no production and we're just starting by adding objects as we go. There's really nothing to baseline in this case. When learning the SCA product for the first time, it can make sense for people to work a little with the migrations scripts first and get a feel for things first sometimes before diving into baselining (simply because there is some complexity with establishing an initial-baseline, and it can make sense to start with more daily-task style things). You have an interesting case, because you're somewhat in the middle of "new" development and "existing database". There is no production yet, but you've already got activity that's been completed in an integration environment so you aren't at the "starting from scratch point" either. (Just reiterating this for readers as the context gets lost sometimes.) So, which to do? If you choose to create a baseline from the integration environment (set it as your "target" on the baseline wizard, use an empty db as "development" as you describe in your first post here), you should be able to deploy from that to an empty database. I just re-ran through that scenario with the PowerShell cmdlets (gist of my simple script here) and it worked -- it will deploy the baseline to the empty database, and then apply incremental migrations on top of that. In this case, in TargetedDeploymentScript.sql there will be a line like "----------------- BEGIN INCREMENTAL MIGRATION: "Migrations\1.0.0-Baseline\001_20190204-1330_kendar.sql" ------------------" This will be followed by all the code from the baseline, then other migrations However, if the database you deploy to isn't totally empty --for example, if you create a user table in it (I created an empty one named "foo") -- that's when I wouldn't expect the deploy to work. SCA detects that the database isn't empty, so it doesn't want to lay down the migration script. Is it possible that this was the case in your initial testing? (The user objects in question could be getting sneakily created by accident by being in model, for example.) In this case, in TargetedDeploymentScript.sql, there will be a line like " PRINT '----- baselined: Migrations\1.0.0-Baseline\001_20190204-1330_kendar.sql (marked as deployed) -----';" The code for the baseline itself won't be in there. In my test, this caused the deployment to simply roll back when it hit errors, since I was using the default option to do it in a transaction If you do already have a lot of objects in the dev/integration environment, it might be useful to track down if this is failing in your case due to deployment target databases not being empty. In that case, I'd personally like to create a baseline, because it seems like a quite convenient way to encapsulate your starting point. As long as when you deploy to dev/qa/uat they are truly empty databases (or I suppose they could be a restored copy of your integration database, just as long as you are 100% sure the baseline doesn't need to be deployed), that should work, from my testing. As to what exactly is happening behind the scenes differently in the MSBuild task, I am not sure on that account. I believe the release artifact functionality may be more recent and may not yet be integrated into all plugins. / comments

That makes sense, thank you for clarifying, @PeterDaniels !Coincidentally, I met with members of the SCA team just this morning to chat about clarifying concepts around baselining in our docs. One ...

0 votes

Yay, glad you solved the case! One experiment I did: I tested putting an object in my model database, and then deployed using SCA to a database name that didn't exist. That worked fine, because in the compare check at the beginning it saw that the database just wasn't there. The object was created based on model and it still deployed the full baseline. Might not be useful if you want to configure the production database specially (files, filegroups, etc) in a way that isn't handled in the pre/post scripts, but just sharing in case it ever comes in handy. I'm currently working on some suggestions for how we can improve the docs about baselining overall, basically adding content that we don't have now that is more clear on what baselines are, when they are useful, and making it easier to get to existing content. Thanks for raising this issue, it's been very useful in terms of thinking through our docs and what would be helpful. / comments

Yay, glad you solved the case!One experiment I did: I tested putting an object in my model database, and then deployed using SCA to a database name that didn't exist. That worked fine, because in t...

0 votes

Hi Peter, The recommended pattern for starting is to create the baseline from your production database. Have you seen this article yet? Working with an existing database. Often the shared Dev database is not in sync with prod (either due to ongoing work or other issues), so prod is preferable to create the baseline. Just checking on this bit first before handing anything further because I'm not sure if you mean in your case that there is no prod yet / new development and ONLY a shared dev database? Kendra / comments

Hi Peter,The recommended pattern for starting is to create the baseline from your production database. Have you seen this article yet? Working with an existing database.Often the shared Dev databas...

0 votes

Woo hoo! I'm really excited about this, I'm a big fan of SCA and can't wait to use it in SSMS. / comments

Woo hoo! I'm really excited about this, I'm a big fan of SCA and can't wait to use it in SSMS.

0 votes

A bit more info about next week's webinar (an alternate format of this is here), and why the topic is important... There has never been a better time to start a project to champion data privacy In a recent Harris poll sponsored by the payment company Stripe, over 1,000 C-level executives were asked to rate which factors they feel are most threatening to their business. The #1 item that executives rated as “somewhat” or “very” threatening to the success of their business is security / data breaches. The #2 rated threat to these businesses? Increased regulation. Data masking mitigates these top threats One of my very first jobs when I began in IT was to build out environments for developer and test teams at a software development company. At first, we didn’t mask any of this data. After problems arose, we began masking only a single field. That was a huge mistake. In this upcoming free webcast, I’ll share the following in just 30 minutes: Why data professionals have a history of neglecting privacy (just like I did in that first job) The three industry drivers for data masking Why regulations have become a top risk to C-level executives Key elements of static data masking tools to consider when evaluating products Pains that people run into when implementing data masking (and how Redgate tools address those pains) An overview of the data masking process Next steps to take in making a case for a data masking project at your organization Now is the time to become a privacy champion Whether or not you are an IT leader, a developer, or a DBA, right now you have a huge opportunity to make a difference for your organization, your customers, and your own career by championing privacy. Yep, your own career! Those top two C-level concerns mentioned at the beginning of this post means that initiating projects like data masking and seeing them through from proof-of-concept to implementation is a big resume-building career move. That’s true whether you choose a Redgate solution, or use the information in this webinar to go a different route. Join me in this upcoming webinar to learn the initial steps that you can make to instigate changes in your company — and to help mitigate the top risks that are keeping C-level executives up at night. Register / comments

A bit more info about next week's webinar (an alternate format of this is here), and why the topic is important...There has never been a better time to start a project to champion data privacyIn a ...

0 votes

Hey Friends, I wrote up a list of reasons why you should take the State of DB DevOps survey today -- it's open until the end of the month! Why You Should Take the ‘State of Database DevOps Survey’ Today (even if you don’t do DevOps) [image] The survey contains 32 questions and should take less than 10 minutes to complete. When I began working with databases, nobody talked about DevOps. It was a few years before I heard the words ‘Agile’ and ‘Extreme Programming’, (which I still read as “EXTREEEEEEMMMMME programmin!”). A lot has changed since then. But a lot hasn’t changed as well. Please help us track the history of how we work with databases by taking the Redgate State of Database DevOps survey today. I believe it’s helpful to our whole community to participate in this survey, and this post explains a few reasons why. The survey… Is hosted by SurveyMonkey, no login is required Takes around 10 minutes Allows you to remain anonymous OR provide contact info to get a chance at winning a $250 Amazon gift card Is for everyone who works with databases, regardless of whether you use DevOps or are a Redgate customer Closes Friday, November 30th The survey creates a history of how we manage database changes I was recently listening to a podcast on CIOs and the Future of IT. The hosts discussed that executives need to be very forwarding thinking, and focus on where the company is going more than where the company is. One side effect of this: executives often think that their organization is ahead of where they actually are, in terms of changing processes and adapting to business initiatives. [image] This makes a lot of sense to me. When I learned to ride a motorcycle, the instructors emphasized that looking forward to where you are going is important when it comes to executing turns correctly. You need to have a wide field of vision and see obstacles, but if you stare at obstacles too much you are more likely to hit them. However, we need a feedback loop! We need all sorts of people who work with databases to discuss what actually happens. This allows Redgate to document and share what’s really happening right now in our technical patterns and practices. You can help us do that by answering the survey (and things like this are why we ask about your job title in the questions). Responding helps us identify and share with you information to help you drive change Ever had an idea which would make a big difference for your organization, but you weren’t sure how to make it catch on? [image] This might be an idea about DevOps, or it might be about data science, cloud adoption, general automation– any project big enough that it’s not simply something you can implement yourself. It’s difficult as a DBA or developer to know how to approach these ideas. Do you need executive support? Is there another way you can help move it forward? The State of Database DevOps survey asks questions about how people have moved projects forward to help map out how change is instigated and sustained in companies. This helps Redgate discover and share with you how you can get projects moving (and you can apply this to projects other than DevOps). Responding provides the community with information on how database development and administration jobs are changing I hear from a lot of folks who are concerned about the future. There’s so much to learn, and it’s increasingly difficult to prioritize between learning more about the tasks you work on today, and learning more about the tools which you may use tomorrow. The results from the State of Database DevOps help show the community: how are roles changing? What’s still the same? This will help you answer those tough questions about what to focus on. Take the survey today! Please share the survey with your colleagues (shortlink: redgate.com/DBDSurvey). And remember, the survey is only open until November 30th, so complete the survey today. / comments

Hey Friends, I wrote up a list of reasons why you should take the State of DB DevOps survey today -- it's open until the end of the month!Why You Should Take the ‘State of Database DevOps Survey’ ...

0 votes

Hi Pete! I saw that you posted this in the SQL Server community slack channel as well, and I've responded there. No problem at all posting in both, just wanted to update you here that messages await you there [image] / comments

Hi Pete! I saw that you posted this in the SQL Server community slack channel as well, and I've responded there. No problem at all posting in both, just wanted to update you here that messages awai...

0 votes

Woo hoo! I am so happy to be part of the team, and part of the forums too [image] / comments

Woo hoo! I am so happy to be part of the team, and part of the forums too

0 votes

How can we help you today?

Kendra_Little

Comments