Viewing 15 posts - 961 through 975 (of 1,654 total)
As always you could answer it depends, but personally I would never do all these tasks in one maintenance plan. Also the frequency of some tasks should be different.
Backups for...
[font="Verdana"]Markus Bohse[/font]
January 10, 2008 at 7:15 am
I don't think that information is stored anywhere in msdb or any other database.
The only place you might find it is the sql server logfile. Restore actions are logged...
[font="Verdana"]Markus Bohse[/font]
January 10, 2008 at 7:03 am
I totally agree with Joe, that you first need to determine what you try to achieve by using more than one filegroup. Also the placement of the files / filegroups...
[font="Verdana"]Markus Bohse[/font]
January 9, 2008 at 1:35 am
Just as the error message says, you exceeded the maximum nesting level of 32. And from my point of view this means there's a serious flaw in your database...
[font="Verdana"]Markus Bohse[/font]
January 8, 2008 at 1:37 am
Why do you want to add another filegroup? Do you experience any problems? Do you want to create a read-only filegroup to shorten maintenance times?
Just because your database is 100...
[font="Verdana"]Markus Bohse[/font]
January 8, 2008 at 1:23 am
In the master and msdb database some stored procedures and functions are added and some are changed. You're user databases won't change. One special case might be if you use...
[font="Verdana"]Markus Bohse[/font]
January 4, 2008 at 6:47 am
Without having experience with the evaluation edition, my guess would be that the server keeps running until you try to restart.
Anyhow the problem seems obvious to me. Go and...
[font="Verdana"]Markus Bohse[/font]
January 4, 2008 at 3:24 am
Ananth,
your second index should be only on dept_id, because the key column of your clustered key (emp_id) will be added automatically to all your non-clustered indexes.
Other than that it...
[font="Verdana"]Markus Bohse[/font]
January 4, 2008 at 2:41 am
Steve Jones - Editor (1/2/2008)
[font="Verdana"]Markus Bohse[/font]
January 3, 2008 at 6:58 am
I remember that being a "bug" in MSDE 2000.
Not sure if any of the service packs fixed it.
My workaround was to edit the job after finishing the maintenance...
[font="Verdana"]Markus Bohse[/font]
January 3, 2008 at 6:57 am
It depends how your SQL Server is licensed. Have a look here for the various licensing options.
[font="Verdana"]Markus Bohse[/font]
January 3, 2008 at 6:50 am
Kevin is right about the IO messages which take too long, but in my experience these messages don't automatically lead to a stack dump. I remember one case like this,...
[font="Verdana"]Markus Bohse[/font]
January 3, 2008 at 5:05 am
The expiration date of a backup only means that it can be removed or overwritten after that date. It does not mean that the backup is automatically removed.
With SQL...
[font="Verdana"]Markus Bohse[/font]
January 2, 2008 at 8:53 am
If you get stack dumps on a regular base you should contact Microsoft PSS and open a support incident. The dump might show (part of) the last query which caused...
[font="Verdana"]Markus Bohse[/font]
January 2, 2008 at 8:47 am
I don't think the descriptions are actually stored in a table. But from BOL here's the overview:
C = CHECK constraint
D = Default or DEFAULT constraint
F = FOREIGN KEY constraint
L =...
[font="Verdana"]Markus Bohse[/font]
January 2, 2008 at 5:21 am
Viewing 15 posts - 961 through 975 (of 1,654 total)