October 19, 2006 at 8:45 am
I'm just starting to learn how to SSMS and am finding it is not as easy as SQLMaint from SS 2000. For instance, I used to creat a maintenance plan that would include integrity checks, full db backups, and tlog backups. You can do that with SSMS but you can't create a separate schedule for each like you can with SQLMaint because it doesn't create a separate job for the full backup and the tlog backup.
Is anyone else as frustrated as me about this?
October 19, 2006 at 9:03 am
Allen,
There are a lot of differences between EM and SSMS.
As for the maint plans, "remove files older then....days" is now replaced with Cleanup Task. Everyone here spent some time figuring this out. Let us know if you need more help.
Regards,Yelena Varsha
October 19, 2006 at 9:08 am
Yeah - it looks like MS has sold out again. They've taken a very simple process and made it into rocket science.
Sorry - just venting.
October 19, 2006 at 12:37 pm
Here's an interesting thread (closed) on the MS feedback page for SQL Server 2005:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124896
I'm not holding my breath.
October 20, 2006 at 6:07 am
Yes. They took a very good, robust, simple process and made more steps and more complicated. I don't know why on earth they removed the easy check box to remove old backups older than ___ from the db maint plan and made you make it a seperate task. I find MGT Studio not as flowing and more difficult to use. Try using it to grant access to 25 tables to the same user... YUCK !
October 20, 2006 at 7:06 am
Markus are you running on SP1?
October 20, 2006 at 7:30 am
Yes I am. SP1 did fix a couple of things in MGT studio.
October 20, 2006 at 8:46 am
>>Try using it to grant access to 25 tables to the same user... YUCK !
It would have been nice if there was an option to "apply script" in the Add object dialog. There's that little script thing at the top of the permissions dialog, but it just lets you *create* script.
IOW: Once you have the script, maybe with a replaceable object name token, you should be able to *use* the script against multiple objects without writing something for the purpose, by using the Add dialog to specify.
In fact, the "create script" button could just write the script in a way that makes this easier. Instead of using explicit object names, it should declare a variable and set the value to the object name you're trying to alter. There should be commented code that allowed the script to be extended to multiple objects.
Just thinking out loud about various ways they could have "cheated" to enhance this without a great deal of UI work. I agree, it would have made more sense to allow multi-select <g>.
>L<
October 20, 2006 at 8:55 am
I guess some things that we currently do in SS2000 we will have to get a little creative when we upgrade. There is one db that we have an outside consulting company make changes to, they give us a db backup when there are changes and I restore it into SQL Svr. I guess I will now have to script the security to the tables for the ID here and simply run that instead of clicking on the checkboxes in the GUI. Seems like some things take a step backwards don't they ?
October 20, 2006 at 9:42 am
My biggest problem with the new maintenance plans is that the backup task resests the destination folder if you open it to modify other properties, such as the database list. It valiantly tries to back up several hundred gigabytes to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup, but they don't fit. The bright side is that it runs much faster that way for the first few databases, compared to the miserable network fileshare it is supposed to use.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply