[font="Verdana"]I hope this feature is included in SQL Server 2008[/font]

[font="Verdana"]You can provide SQLAgentOperatorRole in MSDB so that they will privilege to execute all the jobs.[/font]

[font="Verdana"]Hi,

If the database is in use, SQL Server won't be able to obtain exclusive access to the db for restoring tlogs hence you need to kill those connections to the...

[font="Verdana"]Hi,

You can also try import \ export wizard.

*) Connect to the server and expand database folders

*) Right click on the db and click on All tasks

*) Then click on import...

[font="Verdana"]Hi,

I hope Logshipping cannot handle database file operations, such as adding files etc.[/font]

[font="Verdana"]You can use replication monitor to check the status![/font]

[font="Verdana"]Hi Sumit,

You are right to insert a character other than english you need to declare the column as nvarchar and while inserting the data also use N infront of the...

[font="Verdana"]Hi,

Refer the article "Database Mail", I hope this could help you![/font]

[font="Verdana"]Hi,

I hope the problem is with connection string, can you post the exact connection string you are using in application or the servername you are using in management studio to...

[font="Verdana"]Hi,

Both are some what similar.. In simple transaction log backup will backup all transactions in all objects, where as in transactional replication it will collect the transactions related to the...

[font="Verdana"]If possible check DSN also, sometimes this may be used...

If sa login is used nowhere, then you are safe to reset the password.[/font]

[font="Verdana"]Yes I agree with Micheal, regular shrinking of log file will lead to fragmentation. Hence check why the log file is growing hugely through which process. [/font]

[font="Verdana"]Hi,

I hope only MSXML6 component is alone failed, can you post that log to analyse?? Else you can download MSXML6 setup and try installing the same. Refer the link...

[font="Verdana"]You have missed dir infront of the code, try the below

EXEC master.dbo.xp_cmdshell 'dir C:\SQL2k5_Data'[/font]

[font="Verdana"]Hi,

Since you are working with SQL Server 2005 you can use DMV's to show these informations. DMV's starting with sys.dm_OS* will provide details about operating system

YOu can use the below...