Viewing 15 posts - 5,686 through 5,700 (of 6,678 total)
You can try:
SELECT COUNT_BIG(*)
FROM table_name;
January 14, 2009 at 4:44 pm
Sounds like a case of parameter sniffing. You can look it up in Google and find lots of information about this type of issue.
January 14, 2009 at 4:43 pm
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...
January 13, 2009 at 5:31 pm
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...
January 13, 2009 at 3:30 pm
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...
January 13, 2009 at 1:44 pm
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...
January 9, 2009 at 5:38 pm
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...
January 8, 2009 at 2:27 pm
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...
January 8, 2009 at 2:17 pm
Why would you think the value should be 0? The number of year boundaries being crossed is 1 - therefore the difference is 1.
January 8, 2009 at 1:56 pm
First in regards to what? First of the day - after restarting SQL Server? What?
January 8, 2009 at 11:43 am
Just wait till v2 - which includes full Try/Catch functionality.
January 8, 2009 at 10:38 am
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 -...
January 8, 2009 at 10:26 am
Interesting - you probably have a character in the computer name that is causing a problem.
January 8, 2009 at 10:06 am
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;
January 8, 2009 at 9:26 am
Viewing 15 posts - 5,686 through 5,700 (of 6,678 total)