Viewing 15 posts - 1,021 through 1,035 (of 1,365 total)
You don't need any port related information for configuring linked servers. Just mention the servername if its default installation or servername\instancename in case of named instance.
What error do you...
October 29, 2008 at 3:43 pm
As per version and upgrade matrix on http://msdn.microsoft.com/en-us/library/ms143393(SQL.90).aspx I don't think you will lend up in any problem.
MJ
October 29, 2008 at 2:35 pm
Enable trace flag 3502 which tracks checkpointing of databases in errorlog and see if that helps. There will be flood of messages as its at server level.
MJ
October 29, 2008 at 11:38 am
As David said change the Where clause.
WHERE (CONVERT(datetime, msdb.dbo.backupset.backup_start_date, 102) >= GETDATE() - 7) -This will return backups older than 1 week or 7 days.
Just add the above condition...
October 29, 2008 at 11:02 am
Good one to read once:
http://www.sql-server-performance.com/articles/per/detect_fragmentation_sql2000_sql2005_p1.aspx
HTH,
MJ
October 29, 2008 at 10:50 am
Please make sure that database named "SCom" is not set to simple recovery model. T-log backups cannot be performed with simple recovery model.
MJ
October 24, 2008 at 4:31 pm
Check for sp_dropserver and sp_addserver on books online.
Manu
October 24, 2008 at 9:56 am
Are you able to access any other database on this 2005 instance using ODBC connection?
MJ
October 23, 2008 at 3:30 pm
Check out
http://sqldev.net/sqlagent/SQLAgentRecuringJobsInSecs.htm. The article is for 2000, wouldn't be surprised if it also applies to 2005.
HTH,
MJ
October 22, 2008 at 11:19 am
Yes, you can presume that. Also, you can do one thing(if possible) to check this out:
Do a failover when its okie and nobody will get affected. If it goes to...
October 22, 2008 at 5:52 am
Check the output of
select * from sys.database_mirroring on principal database and verify whether the configuration is fine and mirroring state is synchronized or Synchronizing.
You can also make use...
October 21, 2008 at 4:44 pm
I had to uninstall and install the .NET framework again to make it work. Sorry, I got your suggestion too late.
Thanks again,
Manu
October 20, 2008 at 9:25 am
Have you tried this:
create a job and run it as CMDEXEC. The command to use is
cmd /c /x "Path of the VBS"
Or
Call it like 'wscript C:\temp\file.vbs'
MJ
October 15, 2008 at 3:52 pm
Yes, you can. Please find attached sheet having the same information(High Availability/DR Solutions from Robert Walkins Apress.Accelerated.SQL.Server.2008 book).
HTH
MJ
October 15, 2008 at 3:32 pm
In case you have clustered index on this archive table then try Rebuilding the index(make use of ONLINe=ON if required or do it offline).
HTH
MJ
October 15, 2008 at 12:40 pm
Viewing 15 posts - 1,021 through 1,035 (of 1,365 total)