While it has improved since the NT4 and early Win2000 days, it is only marginally better due to a UI instead of the AT command line. I stopped using the Windows Task Scheduler years ago because you cannot count on it. There are many small applications, both in-house IT as well as distributed, that depend on the reliable SQL Server Agent Job scheduler. This is wrong for any product path/roadmap. I do not understand why Microsoft went through the trouble of removing the Sql Agent scheduler from SQL 2005 Express. Protected static void Backup_Complete(object sender, ServerMessageEventArgs e)Ĭonsole.WriteLine(Environment.NewLine + e.ToString( )) ![]() Object sender, PercentCompleteEventArgs e)Ĭonsole.WriteLine(e.Percent + "% processed.") ![]() Protected static void Backup_PercentComplete( New PercentCompleteEventHandler(Backup_PercentComplete) īu.Complete +=new ServerMessageEventHandler(Backup_Complete) Ĭonsole.WriteLine(Environment.NewLine + "Press any key to continue.") add percent complete and complete event handlers New BackupDeviceItem("AdventureWorks.bak", DeviceType.File) Remember that the Visual Studio C# Express system, is free to use. You will have to compile it and change the values to reflect your server. One option that you could use is the SMO system, Here is a small c# application that backs up a database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |