You really need to review the article I link to in my signature about managing the transaction logs.

In all reality, you are setting yourself up for failure. Either, you...

I don't use Access - so, was not aware that you cannot see synonyms from Access. As far as I know, they should be.

However, what you can do is...

Sorry - but I don't understand what you are trying to do.

If you want users to access to access db1 - but the objects exist in db2, then you create...

Since you only want the mdf/ldf files - I would not worry about trying to access SQL Server. You can use WMI from either VBScript or Powershell - shut...

As far as being able to call a scalar function - not sure I found that anywhere. But, as far as the deprecated features - it's in the documentation...

I missed what you are trying to do - and, you can't do that. You can call a table-valued function through a linked server, but you cannot reference a...

Why would you think the value should be 0? The number of year boundaries being crossed is 1 - therefore the difference is 1.

What is the failure message you are getting?

First in regards to what? First of the day - after restarting SQL Server? What?

Just wait till v2 - which includes full Try/Catch functionality.

You can trap for the errors and display the error messages. Example:

Trap [Microsoft.SqlServer.Management.Common.ExecutionFailureException] {

Write-Output $("Exception: $($_.Exception.Message)");

Write-Output $("Base Exception: $($_.Exception.GetBaseException().Message)");

return;

}

In the above, I am trapping for a specific error -...

Interesting - you probably have a character in the computer name that is causing a problem.

Can you try the following and see what happens?

$computer = 'name of computer';

Get-WmiObject -ComputerName $computer Win32_Service | Where-Object {$_.Name -like 'MSSQL$*'} | Select Name, StartMode, State, Status;

Nigel - that is just one of the reasons we ask for the questions to be posted the way we do. This way we can test a solution that...

The only thing I can suggest is remote into that system and verify that you can access WMI. I have seen things like this when WMI was not working...