After the data refresh (database restore), run this, otherwise the job would be failing;
USE MyDatabase;
GO
EXEC sp_change_users_login 'Update_One', 'MySchma', 'MyUser';
GO
EXEC sp_change_users_login 'Update_One', 'MySchema', 'MyUser';
GO
Shortcuts to run window command with elevated permission
A common trick to run command in elevated permission is to right click and select Run As administrator. Other work arounds are;
- Press Ctrl+Shift+Esc to open the Task Manager. Click on File menu > Run new task. To open a command prompt window, type cmd. Remember to check the Create this task with administrative privileges check-box. Then hit Enter.
- You can also open an elevated command prompt from the Task Manager using CTRL Key.
- Simply open the Start Menu or Start Screen and start typing the command line. Next, hold the Shift and Ctrl keys, and then hit Enter to open the command line in an elevated command prompt.
FIND AND REPLACE using Regular Expression in SSMS
We can use Regular Expression to find and replace, valid with all versions of SSMS
- Find what: {.+}
- Replace with: ‘\1’,
- Look in: Selection
- Expand Find Option
- Use: Regular expression (checked)
That regular expression indicates find everything and remember what we found Replace everything we found \1 by wrapping it with tic marks and a comma.
If you have more complex requirements, the right chevron next to the drop down arrow on Find what lists the regular expression dialect SSMS/Visual Studio understands
References
https://dba.stackexchange.com/questions/96371/applying-quotes-across-multiple-lines
Updating SSIS packages for specific SQL server version
Updating SSIS packages for a specific SQL server target version (valid only for SQL Server 2012 and above)
- Right click on a project, click properties and select your target server version from the drop down
Click Apply, read the warning then click Yes as shown below, and finally click Ok
Re-open the packages and notice how the development platform (control flow and data flow tabs) changes
Before
After
Check for any odd behavior (discontinued/deprecated tasks), build/rebuild your packages, test your packages, and deploy/redeploy them.
Start Debugging vs Start Without Debugging
Start Debugging
Start Debugging (pressing F5) is the normal way of launching your application in visual studio. Debugger would be attached automatically and you can expect to see debugging messages and breakpoints in your application.
A popular misconception is that Debugger doesn’t come into play for Release build. This isn’t true. Set a breakpoint in a Release build and then press F5 to see if it stops there. Some debugging messages are not happening in Release build for example message from System.Diagnostics.Debug class.
Start without Debugging
This will start the application (pressing CTRL + F5) without the debugger attached. That’s it. If we need to attached the debugger to this process afterwards, we can select Debug->Attach to Process option.
For further info, please follow this link;
https://blogs.msdn.microsoft.com/zainnab/2010/11/01/start-debugging-vs-start-without-debugging/