(Can’t wait? Download it right now!<\/a> Rather have the highlights in bullet-point form? Click here for a concise changelog<\/a>.)<\/p>\n Now on to the good stuff:<\/p>\n Just like too much ghost pepper sauce on your enchilada, a mistake made while editing a SQL job can smolder for a while before you realize something is wrong.\u00a0 As the heat compounds, it may not be clear how to actually fix<\/em> the mess you’re in.\u00a0 Here’s a tip:\u00a0 Chug a glass of milk and check your version control server.\u00a0 If you’ve been committing after every change you’ll be able to see exactly what happened and how to get back to something pleasantly spicy.<\/p>\n Cheers to Alon R., Herbert B., Jim W., and Michael A. for requesting this feature \ud83c\udf7b<\/p>\n Pizza at a Chinese buffet?\u00a0 Mac and cheese on a Mexican menu?\u00a0 Assemblies in a SQL database?\u00a0 Somebody<\/em> must be ordering those, because they exist.\u00a0 If that’s you… well, you be you.\u00a0 Go ahead and save those assemblies to version control.\u00a0 Fair warning: Unless you speak base64-encoded binary, it’ll be hard to tell later what exactly your version control server is serving you.\u00a0 Take good notes.<\/p>\n Maybe you’re on the other end of the spectrum, ordering esoteric dishes with a perfect accent.\u00a0 More scripts, coming right up!\u00a0 If fancy indexes are your jam, you’ll find them on your table (script) without asking twice.\u00a0 Database-wide triggers, too.\u00a0 Thanks Sam F. for the call-in!<\/p>\n Nothing says homestyle cookin’ like a friendly smiley to say hello when you walk in.\u00a0 VersionSQL has learned a new skill: Hospitality.<\/p>\n If you’re a regular, don’t worry.\u00a0 The servers know your usual and will stay out of your way.<\/p>\n <\/p>\n Things get busy, I understand.\u00a0 It’s easy to let the little things slide, like checking your changes in to version control.\u00a0 A little nudge can make all the difference.\u00a0 And if you need a little more time, just say so.\u00a0 We’ll check in later.<\/p>\n SQL Server is not case-sensitive (except when it is<\/a>).\u00a0 The Windows filesystem is not case-sensitive (but can be<\/a>).\u00a0 Git is case-sensitive (but can try not to be<\/a>), and Subversion too (ditto<\/a>).\u00a0 So what happens when you rename a table in SQL Server\u00a0but only change its case<\/em> (e.g. test -> TEST)?\u00a0 Well, VersionSQL’s got your back.\u00a0 It’s not going to scan for objects where the only<\/em> change is the name casing (that’d waste a lot of time), but if you’ve edited the script\u00a0and<\/em> changed the object’s casing it’ll pass the case change along to version control too.\u00a0 Thanks Eric G. for help untangling this.<\/p>\n I was surprised and gratified to learn that KDiff3 is still undergoing active development<\/a>.\u00a0 VersionSQL now knows how to find and use it for diff and merges.<\/p>\n The thing that bugs me the most about modern software is when it doesn’t respond to my input instantly<\/em>.\u00a0 SSMS does a lot of things behind the scenes when you right-click on a database, but one thing it’s\u00a0not<\/em> doing now is waiting on VersionSQL.\u00a0 VersionSQL 1.8 pre-caches the tiny bit of server info that it needs in order to display the correct context menu entries as quickly as possible.\u00a0 Granted, that only saves 30-70 milliseconds, but it’s your<\/em> valuable time. Every little bit helps.<\/p>\n There’s a difference<\/a> in interpretation<\/a> about the “newline” character (aka “end of line” character – see the confusion?). VersionSQL now ends the final line of each script with a newline. Here’s why: If the file doesn’t end with a newline, the next time you add a line to the end of the file your diff tool will show you that two lines have changed (the line you added, but also the previous line because that newline character had to be added first).\u00a0 This change makes for more understandable diffs.<\/p>\n \ud83c\udf54 Commit shows a warning instead of an error if a table is deleted during scripting (thanks P\u00e9ter!)<\/p>\n \ud83e\udd5e Contact form now drops out to the browser if an unusable proxy is specified<\/p>\n \ud83c\udf55 File overwrite bug caused script fragments to remain if the script being committed was shorter than the one already in the repo (thanks Alon and Sam!)<\/p>\n \ud83e\udd6a Ignored objects are now excluded from batch scripting, not just from change detection (thanks again P\u00e9ter!)<\/p>\n \ud83e\udd57 In rare circumstances, a git commit could be created with the timestamp of a previous commit (thanks Tor!)<\/p>\n \ud83c\udf2d Manual update check now shows a descriptive message if the update server is unavailable<\/p>\n \ud83c\udf68 No longer attempts to push an empty git commit if an error occurred while building the commit<\/p>\n \ud83c\udf70 No longer writes to the error log when a diff started from the commit message prompt aborts due to missing configuration<\/p>\n Thanks for reading!\u00a0 Compliments to the beta testers.<\/p>\n How about an appetizer? Download VersionSQL<\/a><\/p>\n Ready to place your order? Purchase VersionSQL<\/a><\/p>\n Need more time? Request an extended trial<\/a><\/p>\n\n
\n
\n
\n
Main Courses<\/h2>\n
SQL Server Agent Job Scripting<\/h3>\n
![](\"\/images\/wn-1.8-jobs.gif\")
<\/p>\nAssembly, DDL Trigger, Spatial and Full-Text Index Scripting<\/h3>\n
Side Dishes<\/h2>\n
Welcome Toasts<\/h3>\n
![\"\"](\"https:\/\/www.versionsql.com\/help\/wp-content\/uploads\/2022\/02\/wn-1.8-welcome-2.gif\")
<\/p>\nReminder Toasts<\/h3>\n
![\"\"](\"https:\/\/www.versionsql.com\/help\/wp-content\/uploads\/2022\/02\/wn-1.8-reminder.gif\")
<\/p>\nGarnishes<\/h2>\n
Case Change Propagation<\/h3>\n
KDiff 1.8+ Presets<\/h3>\n
Minimized Context Menu Delay<\/h3>\n
Script Termination Character<\/h3>\n
Bugfixes<\/h2>\n
Wrapping Up<\/h2>\n