Viewing 15 posts - 1,321 through 1,335 (of 2,387 total)
Run command cluster.exe /CLUSTER:yourclustername group from xp_cmdshell and insert the result into a temp table.
August 13, 2003 at 8:55 am
What about SELECT *
FROM ::fn_virtualservernodes()
August 13, 2003 at 8:30 am
declare @dbname varchar(50)
declare dbname cursor
for select name from master..sysdatabases
open dbname
fetch next from dbname into @dbname
while @@fetch_status = 0
begin
select @message = 'select name, filename from ' + @dbname...
August 12, 2003 at 2:14 pm
You may try to perform log backup immediately after noticing something wrong with your database. If the log file is totally inaccessable, you will lose all transactions since last log...
August 12, 2003 at 1:21 pm
If it is default instance, you can rename it by change the machine name.
If it is named instance, you have to uninstall and reinstall.
Or create server alias (the name you...
August 12, 2003 at 12:22 pm
The uncommitted transactions will be lost. In order to minimize the lose, backup the transaction more frequent you can.
August 12, 2003 at 12:11 pm
No, you can't. You have to uninstall and re-install SQL Server.
August 12, 2003 at 11:45 am
Can you post complete error message when query the linked sevrer with four part name?
Is the MDAC in same version on your old and new servers?
August 12, 2003 at 11:36 am
August 12, 2003 at 8:32 am
Do you want to reduce the log file size?
1. dbcc sqlperf(logspace) will tell you log file size and spaced used.
2. backup log yourdbname with truncate_only to truncate the inactive...
August 12, 2003 at 7:04 am
So you did recreate the linked server in your new machine, what error message did you receive when you can't connect to it? What type of likned server are you...
August 12, 2003 at 6:54 am
It is not connection string in sp_who or sp_who2. The application has to be designed to use the workstation ID in the connection string.
Andy's article explains quite clear.
August 12, 2003 at 6:48 am
You are right. Either they are talking windows 2003 or clustering solution from third party like Veritas.
August 12, 2003 at 6:43 am
The connect string has to include "Workstation ID" parameter in the application.
August 12, 2003 at 6:26 am
Restore MSDB database to another server, script the job and recreate it.
August 11, 2003 at 10:01 am
Viewing 15 posts - 1,321 through 1,335 (of 2,387 total)