On the Initiate Restore tab, choose Azure Blobs (Azure Storage) as the Datasource type and select the Backup Instance you want to restore. The backup instance is the storage account that contains the blobs you want to restore. On the Select recovery point tab, select the type of backup you want to restore.

Just whole integers, maybe up to 20 if the customer gets real bad, or excited about their swimming pool while it's being built. If it ain't broke don't fix it Discover my world at jkirkerx.com

I once attended a department meeting with probably 150 developers (actual developers and not support) where among other things the VP that was in charge congratulated the initiative of a single developer who created a pass through API that allowed one large system to access functionality via another large system. Must be good right? Except I knew there was a team of 4 developers that had been working on exactly the same thing for several months. I knew this because I needed that functionality and I had been blocked because they were not close to being done. I always wondered if the VP had any idea what was going on in the dept that he ran.

This is an example of why I always insist on tabs as a separator (not commas nor semi-colons.) Guus2005 wrote: Remove all double quotes not directly preceded or directly followed by a semicolon You are trying to solve this incorrectly. Guus2005 wrote: 1;200;345;"Apotheker "Blue tongue"";"Apeldoorn";12;"ABCD12" You do not want to "remove" the double quotes because they are part of the value. The following is the correct value from the above. Apotheker "Blue tongue" The pattern for the CSV is as follows 1. Semi-colon separates values. 2. Some values are quoted (double quotes.) For processing for the second case the following applies for the value (not the line but just a value from the line.) 1. The double quotes MUST be at both the end and start of the value. It is ignored if both are not true. 2. The double quotes in that case are removed. Double quotes internal are not impacted. Additionally you need to deal with the potential that there is a semi-colon in the middle of a value. If there is a semi-colon in a value then I doubt you should be using a regex to parse lines. Certainly if I was doing it I would not use a regex. Rather I would build a parser/tokenizer since the rules would be easier to see (and debug). Additionally it would probably be faster also. The tokenizer makes the case with the semi-colon much easier to deal with. The tokenizer rule would be in general 1. Find a semi-colon (start at semi-colon.) 2. If the next character is a double quote, flag a rule that it must look for quote then semi-colon as next break. 3. If the next character is not a double quote, flag a rule that it must look for a semi-colon as next break.

Mircea Neacsu wrote: I would go for mid to late '90-es....I've used the ARM (Annotated Reference Manual) by Stroustoup and Elli However the 90s was when libraries for C/C++ started to become available. But Stroustrup was documenting the language and nothing else. And the Ellis book (80s) did the same but more on using it rather than what it was. So as I already mentioned in the 90s of the many libraries I used I found only one that had good documentation. There were more good books published in the 90s (Meyers and Ellis) but those were still on using C++. So they expanded what what already there but the additional stuff was not documented.

I think Exceptions should be handled where they can be handled. Input data should always be validated - on any level. Not doing this in the low level code is the cause of the majority of the security bugs. By example: buffer overflow, caused by the high level part (wrong data in the parameters), not checked and not handled in the low level code, and voila, we have a security problem.

samflex wrote: The method says Update(...) No, it says updateSal_Click(object sender, EventArgs e), which is clearly an event handler that is called when the user clicks a button or other control. And the result of the LINQ query is returned in the Text field of the newTotal item, which is most likely a field on the form.

I'd also add that taking a look at W3Schools Online Web Tutorials[^] can be a fun little exercise. It tends to be really basic level stuff, but you can take a look at a lot of varied technologies to see if any catch your eye. Then you can do research from there.

Myself I would first look for a commercial solution. Rolling your own requires dealing with all of the possible error scenarios and notifications that must occur when an error happens. But other than that there are two problems not one. So there should be two solutions. 1. Do the back up 2. Move the back up to the remote location.

STRING_AGG is the best approach for SQL Server 2017 or later. If you need to support earlier versions, you'll need an alternative: Concatenating Row Values in Transact-SQL - Simple Talk[^] "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

v1 - CodeProject[^] M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.

v4 - CodeProject[^] M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.

I always use parens. Removes the question for me an future maintenance programmers as to what I thought the precedence was.

That's pretty clever. my mind was no where near thinking of it like that. And it runs pretty quick as well, and gives me exactly what I want with null records on a failed join. This opens up new possibilities for me with some of the business logic. On a side note, I'm surprised that I didn't get laughed at for wanting to craft something like this. I couldn't think of a better way to handle this without writing a bunch of extra functions that might not be fast and reliable. Thanks Richard! If it ain't broke don't fix it Discover my world at jkirkerx.com

SSRS have a subscription option where you manage the published reports and have the report emailed to whoever at a scheduled time. The SQL server needs to be setup for email. (SSMS - Maintenance - Database Mail) This is available on the standard version if you have the appropriate rights. A Fine is a Tax for doing something wrong A Tax is a Fine for doing something good.