Viewing 15 posts - 61 through 75 (of 171 total)
It is stored as a SSIS (SQL Server Integration Services) package.
I think that you have to use SQL Server Business Intelligence Development Studio to change it. This is however not...
July 28, 2008 at 11:29 am
My understanding is that the SQL Server 2005 Maintenance Plans are stored as SSIS packages in the system table msdb.sysdtspackages90.
I have a set of maintenance stored procedures that you could...
July 28, 2008 at 10:45 am
SQL Server Central thread:
"Under SQL Server 2005, we have found that we are having a problem with our maintenance plans. Since most of our servers are on VMWare, when we...
July 27, 2008 at 9:35 am
I think that the issue that you're experiencing is also the same issue that was reported on Microsoft Connect recently.
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=357953
Ola Hallengren
July 27, 2008 at 6:50 am
I have a stored procedure that you could use to dynamically rebuild your indexes online or offline. In your case the clustered index on the table with a LOB column,...
July 25, 2008 at 2:26 pm
Here's a short summary. The person in this thread is describing an issue that is very similar to yours. I think that it is the same issue. He has been...
July 25, 2008 at 9:10 am
I read about a similar problem on another forum recently.
http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SQL-Server-2005/Q_23452193.html
In case you are thinking about using a T-SQL solution, I have a set of maintenance stored procedures that you are...
July 17, 2008 at 3:48 pm
The stored procedure has been designed to continue to the next index if the rebuild or reorganize of an index would fail. I have some information about this under Error...
July 11, 2008 at 8:44 am
I think that a small index (low page_count) could have a fragmentation that does not go away even if you rebuild the index.
In addition fragmentation on small indexes has a...
July 8, 2008 at 2:59 pm
The stored procedure is checking for this. INDEX_REBUILD_ONLINE is only allowed when SERVERPROPERTY('EngineEdition') = 3.
You could run it like this.
EXECUTE dbo.IndexOptimize
@databases = 'USER_DATABASES',
@FragmentationHigh_LOB = 'INDEX_REBUILD_OFFLINE',
@FragmentationHigh_NonLOB = 'INDEX_REBUILD_OFFLINE',
@FragmentationMedium_LOB =...
July 8, 2008 at 2:50 pm
You need to download and create the objects CommandExecute and DatabaseSelect too or use the installation script MaintenanceSolution.sql.
http://ola.hallengren.com/scripts/MaintenanceSolution.sql
I would create all objects in the master database or in a custom...
July 8, 2008 at 1:52 pm
You need to install SP2. The function OBJECT_SCHEMA_NAME is new in SP2.
I have some information about this in the Frequently Asked Questions section.
http://ola.hallengren.com/frequently-asked-questions.html
You could create the objects in any database....
July 8, 2008 at 11:35 am
>Forgot to add the WITH INIT clause to my BACKUP job.
Just consider the risk with overwriting your existing backup before the new backup has succeeded.
Ola Hallengren
June 28, 2008 at 7:52 am
I have a stored procedure that I think could be useful for you. It is doing index optimization.
http://ola.hallengren.com/sql-server-index-and-statistics-maintenance.html
One feature is that it is doing an extra check that the index...
June 27, 2008 at 12:16 pm
Microsoft has as whitepaper on this.
"Generally, you should not be concerned with fragmentation levels of indexes with less than 1,000 pages. In the tests, indexes containing more than 10,000 pages...
June 25, 2008 at 1:52 pm
Viewing 15 posts - 61 through 75 (of 171 total)