Currently have an issue where most of the time shutting down the PC just performs a restart, annoying to say the least, been going on since late 2018.
I’m currently trying out this solution to see if it can be resolved.
6-Dec-19: A couple of test shutdowns later and it seems to be working, one to monitor.
If you repeatedly use a Remote Desktop session and that session needs access to files on the machine you’re connecting from then you’d normally set up a network drive, possibly mapped as follows:
net use z: \\yourmachine\c$ /persistent:Yes
But, depending on how Draconian your network security is then mapping folders on user machines may actually be blocked. Strange one as this ability is mostly essential when working on a remote machine, especially if a developer. Fortunately you can map using the built in sharing of RDP. Same format as earlier just the machine name changes and effectively becomes a constant, so the mapping is now:
net use z: \\tsclient\c /persistent:Yes
And job done, until the next group policy is introduced blocking that…
See this link for details on how to use
An example, that retrieves all view names on the current server follows:
DECLARE @command varchar(100)
SELECT @command = 'USE ?; SELECT name FROM sysobjects WHERE type = ''V'' ORDER BY name'
EXEC sp_MSforeachdb @command
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,
Try this solution, posted as a fix for Windows 7 but worked for me under Windows 10.
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.
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)
Having problems setting, and retaining, the Updater Proxy in the Notepad++ UI?
Then resort to the command line. Open a cmd prompt, with administrator privileges.
At the prompt go to the Notepad++ updater directory, the following works for default installations:
cd C:\Program Files (x86)\Notepad++\updater
From here run this command:
This brings up the same dialog as the UI but this time the values you enter will be saved.