Maintenance Plan Wizard doesn't see my DB

Using SQL2005-Std, the Maintenance Plan Wizard doesn't see my database. My
database is not listed in the dialog box where you select specific databases
to backup. I see AdventureWorks, AdventureWorksSW, master, model and msdb.
Object Explorer doesn't show "msdb". Maybe it is my DB ? Strange because my
DB has another name and is configured as SQL7 compatible.
--
Francois PIETTE
http://www.overbyte.beMaint plan doesn't support database in 70 or lower compat mode.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Francois PIETTE" <fpiette@.newsgroups.nospam> wrote in message
news:%23C5Jhp8aHHA.4176@.TK2MSFTNGP02.phx.gbl...
> Using SQL2005-Std, the Maintenance Plan Wizard doesn't see my database. My
> database is not listed in the dialog box where you select specific databases
> to backup. I see AdventureWorks, AdventureWorksSW, master, model and msdb.
> Object Explorer doesn't show "msdb". Maybe it is my DB ? Strange because my
> DB has another name and is configured as SQL7 compatible.
> --
> Francois PIETTE
> http://www.overbyte.be
>|||Hi, Francois,
I understand that you could not see your database with compatibility level
70 in your Maintenance Plan.
If I have misunderstood, please let me know.
This is a known by design issue. Tibor has explained the reason here.
For now, the workaround is that you change the compatibility level to 80 or
90.
Please feel free to let us know if you have any other questions or concerns.
Have a good day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||> I understand that you could not see your database with
> compatibility level 70 in your Maintenance Plan.
Right.
> This is a known by design issue. Tibor has explained the reason here.
> For now, the workaround is that you change the compatibility
> level to 80 or 90.
> Please feel free to let us know if you have any other questions or
concerns.
I have an existing application running with SQL version 7 that I want to run
on SQL2005. That's why I selected compatibility level 70.
a) If I change the compatibility level to 80 or 90, what kind of problem
could I have ? I have to say that I have no control over the application and
will not be able to fix any request or stored procedure.
b) Is changing the compatibility level a revertible process ? If I change
the compatibility level from 70 to 90, then create the maintenance plan, can
I go back to level 70 and still use the maintenance plan and the DB ?
c) If none of the above strategy work, how am I supposed to automate backup,
integrity check, reindexation and all similar maintenance tasks wih the
"level 70" database ?
--
Francois PIETTE
http://www.overbyte.be|||Hi,
For your three questions, please see the following answers:
>a) If I change the compatibility level to 80 or 90, what kind of problem
> could I have ? I have to say that I have no control over the application
and
> will not be able to fix any request or stored procedure.
If there are some features or functionalities that SQL Server 2005 does not
support but still exist in your application, it may not work.
Please refer to:
SQL Server 2005 Database Engine Backward Compatibility
http://msdn2.microsoft.com/en-us/library/ms143532.aspx
Since it is critical to your application, I do not recommend that you
change the compatibility level. You may consider to write T-SQL script and
execute it in SQL jobs. Anyway this depends on your requirements. Could you
please let us know what your requirements are?
> b) Is changing the compatibility level a revertible process ? If I change
> the compatibility level from 70 to 90, then create the maintenance plan,
can
> I go back to level 70 and still use the maintenance plan and the DB ?
Yes, the database can change back to 70 if the SQL Server 2005 new features
were not used in your database; For the maintenance plan, I recommend that
you established a test environment to check if it still work since I have
not found any document talking about this issue.
>c) If none of the above strategy work, how am I supposed to automate
backup,
>integrity check, reindexation and all similar maintenance tasks wih the
>"level 70" database ?
As I replied in your first question, you can write T-SQL statement in one
or several SQL jobs and schedule them to run. For example:
BACK UP DATABASE
===================BACKUP DATABASE Test To DISK='D:\SQLDB_BACKUP\Test.bak'
CHECK INTEGRITY
=================USE [TEST]
GO
DBCC CHECKDB WITH NO_INFOMSGS
GO
INDEX DEFRAGEMENT
=====================DBCC INDEXDEFRAG Test
GO
INDEX REBUILDING
======================DBCC DBREINDEX 'Test.dbo.tblTest'
GO
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Thanks, this perfectly answer my question.
Very good support as usual.
--
Francois PIETTE
http://www.overbyte.be
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> a écrit dans le message
de news:x9I%234XGbHHA.928@.TK2MSFTNGHUB02.phx.gbl...
> Hi,
> For your three questions, please see the following answers:
> >a) If I change the compatibility level to 80 or 90, what kind of problem
> > could I have ? I have to say that I have no control over the application
> and
> > will not be able to fix any request or stored procedure.
> If there are some features or functionalities that SQL Server 2005 does
not
> support but still exist in your application, it may not work.
> Please refer to:
> SQL Server 2005 Database Engine Backward Compatibility
> http://msdn2.microsoft.com/en-us/library/ms143532.aspx
> Since it is critical to your application, I do not recommend that you
> change the compatibility level. You may consider to write T-SQL script and
> execute it in SQL jobs. Anyway this depends on your requirements. Could
you
> please let us know what your requirements are?
> > b) Is changing the compatibility level a revertible process ? If I
change
> > the compatibility level from 70 to 90, then create the maintenance plan,
> can
> > I go back to level 70 and still use the maintenance plan and the DB ?
> Yes, the database can change back to 70 if the SQL Server 2005 new
features
> were not used in your database; For the maintenance plan, I recommend that
> you established a test environment to check if it still work since I have
> not found any document talking about this issue.
> >c) If none of the above strategy work, how am I supposed to automate
> backup,
> >integrity check, reindexation and all similar maintenance tasks wih the
> >"level 70" database ?
> As I replied in your first question, you can write T-SQL statement in one
> or several SQL jobs and schedule them to run. For example:
> BACK UP DATABASE
> ===================> BACKUP DATABASE Test To DISK='D:\SQLDB_BACKUP\Test.bak'
> CHECK INTEGRITY
> =================> USE [TEST]
> GO
> DBCC CHECKDB WITH NO_INFOMSGS
> GO
> INDEX DEFRAGEMENT
> =====================> DBCC INDEXDEFRAG Test
> GO
> INDEX REBUILDING
> ======================> DBCC DBREINDEX 'Test.dbo.tblTest'
> GO
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> Get notification to my posts through email? Please refer to:
>
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> If you are using Outlook Express, please make sure you clear the check box
> "Tools/Options/Read: Get 300 headers at a time" to see your reply
promptly.
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no
rights.
> ======================================================>
>
>|||Hi,
Appreciate your update and response. I am glad to hear that the suggestions
are helpful. If you have any other questions or concerns, please do not
hesitate to contact us. It is always our pleasure to be of assistance.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================