See this link for details on how to use
Changes to the script debugging setting coming in a future update:
Need to find a column in a database? The following SQL will return the tables, and columns, that contain a wildcard value
SELECT c.name AS ColumnName, t.name AS TableName FROM sys.columns c JOIN sys.tables t ON c.object_id = t.object_id WHERE c.name LIKE '%column_name%' ORDER BY TableName, ColumnName;
Try this solution, posted as a fix for Windows 7 but worked for me under Windows 10.
This is a quick aid based on the Raspberry Pi documentation.
Some basic commands are:
sudo nginx -s reload sudo nano /etc/nginx/nginx.conf systemctl status nginx.service
Quick post, aide-memoire, for disabling and then re-instating database contraints in MS-SQL.
EXEC sp_MSforeachtable "ALTER TABLE ? NOCHECK CONSTRAINT ALL" EXEC sp_MSforeachtable @command1="PRINT '?'", @command2="ALTER TABLE ? WITH CHECK CHECK CONSTRAINT ALL"
Since I installed the “Windows 10 Fall Creators Update”, build 16299, the desktop has stopped auto-starting, to it’s BIOS configured schedule. It’s scheduled for a 5:01am start, but every morning I’ve come into the room, since the update, it’s sitting there switched off.
A couple of Google’s later and here’s the answer, well I hope it is as I haven’t verified it yet, something for tomorrow morning. So the suggestion is to disable Windows “fast startup” mode, details on doing that can be found over at TechAdvisor.co.uk, and a more detailed explaination of why is at HowToGeek.com.
29th October 2017: Seems to have resolved the issue.
Possibly an issue with Pi firmware of 4.9.x, find out your version by using this command
If so then issue these commands, the first installs the firmware updater the second the 4.4.50 version of the firmware.
sudo apt-get install rpi-update sudo rpi-update 52241088c1da59a359110d39c1875cda56496764
If you can’t install the firmware because you have a “custom” kernel then you’ll have to get the latest version of Raspbian and install that, then run the above two commands.
When running a SQL script using the command sqlcmd tool if you switch context to another database, by using the “use database” command, then any variables defined before this are lost. A similar thing happens if you use the “go” command to group, or batch, commands in the script.
Create a temporary table, e.g
CREATE TABLE #GlobalVariables (variableOne varchar(30), variableTwo int) INSERT INTO #GlobalVariables (variableOne, variableTwo) VALUES ('ABCdef', 222222)
Use script variables
:setvar variableOne "ABCdef" :setvar variableTwo 222222
To access these in your SQL code you would do the following:
UPDATE #GlobalVariables SET variableOne = '$(variableOne)', variableTwo = $(variableTwo)