managed objects

Hello people :-)

I'm doing some development work with Visual Studio 2005 and SQLServer 2000. My SQL DB is running on a Windows 2000 Server box in the office, and I'm doing the development on my XPPro workstation. Now I've been trying to connect to the Win2000 box though VS and although I can see the server and the DB when I hit ok I get this error

"The SQL server specified by these connection propertise does not support managed objects"

What the heck does that mean?

any help would be great :-)Well when you are using VS2005 it assumes you are connecting to SQL Server 2005, quick fix I think is to install .NET framework 2.0 in the Win2k server and make sure IIS is running even if you are not using it. Hope this helps.

Make the Login box go away!

I'm trying to incorporate the /ReportServer virtual into our application web
site so we can point the Report Viewer control to /ReportServer rather than
<default web site's IP>/ReportServer. I'm trying to remove authentication
from <app>/ReportServer, but I've been unable to keep it from popping up
that blasted login dialog box. I've briefly tried using the FormsAuth
sample and even rewrote it to always return True from all the authentication
functions, but neither solved my problem.
The application is under Forms Auth. I just want the ReportServer virtual
to run in that context. At this point, I don't even care if it's really
keeping authentication or just letting anyone who happens to type in
http://<our_app>/ReportServer go uncontested. It's extremely frustrating,
and it doesn't work for any users as it is now.
This is SQL Server Standard, so I don't know if custom security extensions
(assuming I really had any clue as to how they worked or how to set them up)
would even work (I came across a page that says only Enterprise supports
them).To my knowledge, for IE to give your windows authentication credentials
automatically to IIS, you have to adresse the website using a machine name.
Use something like http://computername/ReportServer
Suppose your server is named BigBox.leetdomain.com
Address it using http://BigBox/ReportServer
I never had to mess around with the report server security as we want
windows authentication and the report server will not be used externally. It
seems to be configured fine by default.
"DJM" wrote:
> I'm trying to incorporate the /ReportServer virtual into our application web
> site so we can point the Report Viewer control to /ReportServer rather than
> <default web site's IP>/ReportServer. I'm trying to remove authentication
> from <app>/ReportServer, but I've been unable to keep it from popping up
> that blasted login dialog box. I've briefly tried using the FormsAuth
> sample and even rewrote it to always return True from all the authentication
> functions, but neither solved my problem.
> The application is under Forms Auth. I just want the ReportServer virtual
> to run in that context. At this point, I don't even care if it's really
> keeping authentication or just letting anyone who happens to type in
> http://<our_app>/ReportServer go uncontested. It's extremely frustrating,
> and it doesn't work for any users as it is now.
> This is SQL Server Standard, so I don't know if custom security extensions
> (assuming I really had any clue as to how they worked or how to set them up)
> would even work (I came across a page that says only Enterprise supports
> them).
>
>|||The Forms Authentication sample from MSDN gives you instructions on how to
restore to default non-forms-authentication settings.
Basically, it's not recommended since you'll have to re-do your report
permissions. And if you don't have the original .config files backed up,
you'll have a VERY difficult time.
--
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"DJM" <msnews@.puddlestheshark.com> wrote in message
news:e6Cz03NzEHA.2600@.TK2MSFTNGP09.phx.gbl...
> I'm trying to incorporate the /ReportServer virtual into our application
> web
> site so we can point the Report Viewer control to /ReportServer rather
> than
> <default web site's IP>/ReportServer. I'm trying to remove authentication
> from <app>/ReportServer, but I've been unable to keep it from popping up
> that blasted login dialog box. I've briefly tried using the FormsAuth
> sample and even rewrote it to always return True from all the
> authentication
> functions, but neither solved my problem.
> The application is under Forms Auth. I just want the ReportServer virtual
> to run in that context. At this point, I don't even care if it's really
> keeping authentication or just letting anyone who happens to type in
> http://<our_app>/ReportServer go uncontested. It's extremely frustrating,
> and it doesn't work for any users as it is now.
> This is SQL Server Standard, so I don't know if custom security extensions
> (assuming I really had any clue as to how they worked or how to set them
> up)
> would even work (I came across a page that says only Enterprise supports
> them).
>
>|||But the standard is Windows Authentication. I still get the
username/password dialog when trying to access a report via report viewer
control from my website.
"Jeff A. Stucker" <jeff@.mobilize.net> wrote in message
news:O$FUn9OzEHA.3708@.TK2MSFTNGP14.phx.gbl...
> The Forms Authentication sample from MSDN gives you instructions on how to
> restore to default non-forms-authentication settings.
> Basically, it's not recommended since you'll have to re-do your report
> permissions. And if you don't have the original .config files backed up,
> you'll have a VERY difficult time.
> --
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "DJM" <msnews@.puddlestheshark.com> wrote in message
> news:e6Cz03NzEHA.2600@.TK2MSFTNGP09.phx.gbl...
>> I'm trying to incorporate the /ReportServer virtual into our application
>> web
>> site so we can point the Report Viewer control to /ReportServer rather
>> than
>> <default web site's IP>/ReportServer. I'm trying to remove
>> authentication
>> from <app>/ReportServer, but I've been unable to keep it from popping up
>> that blasted login dialog box. I've briefly tried using the FormsAuth
>> sample and even rewrote it to always return True from all the
>> authentication
>> functions, but neither solved my problem.
>> The application is under Forms Auth. I just want the ReportServer
>> virtual
>> to run in that context. At this point, I don't even care if it's really
>> keeping authentication or just letting anyone who happens to type in
>> http://<our_app>/ReportServer go uncontested. It's extremely
>> frustrating,
>> and it doesn't work for any users as it is now.
>> This is SQL Server Standard, so I don't know if custom security
>> extensions
>> (assuming I really had any clue as to how they worked or how to set them
>> up)
>> would even work (I came across a page that says only Enterprise supports
>> them).
>>
>|||And since the report server *is* being accessed externally, it's quite
definitely not fine for our needs.
"/dev/null" <devnull@.discussions.microsoft.com> wrote in message
news:2BD4677A-BEF2-4048-92B9-316F38813E85@.microsoft.com...
> To my knowledge, for IE to give your windows authentication credentials
> automatically to IIS, you have to adresse the website using a machine
> name.
> Use something like http://computername/ReportServer
> Suppose your server is named BigBox.leetdomain.com
> Address it using http://BigBox/ReportServer
> I never had to mess around with the report server security as we want
> windows authentication and the report server will not be used externally.
> It
> seems to be configured fine by default.
>
> "DJM" wrote:
>> I'm trying to incorporate the /ReportServer virtual into our application
>> web
>> site so we can point the Report Viewer control to /ReportServer rather
>> than
>> <default web site's IP>/ReportServer. I'm trying to remove
>> authentication
>> from <app>/ReportServer, but I've been unable to keep it from popping up
>> that blasted login dialog box. I've briefly tried using the FormsAuth
>> sample and even rewrote it to always return True from all the
>> authentication
>> functions, but neither solved my problem.
>> The application is under Forms Auth. I just want the ReportServer
>> virtual
>> to run in that context. At this point, I don't even care if it's really
>> keeping authentication or just letting anyone who happens to type in
>> http://<our_app>/ReportServer go uncontested. It's extremely
>> frustrating,
>> and it doesn't work for any users as it is now.
>> This is SQL Server Standard, so I don't know if custom security
>> extensions
>> (assuming I really had any clue as to how they worked or how to set them
>> up)
>> would even work (I came across a page that says only Enterprise supports
>> them).
>>
>>|||Ok, I've set Authentication mode="None", I've set the /ReportServer virtual
to allow Anonymous access as IUSR, I've granted IUSR_GROUP (local group
containing the IUSR, IWAM, and ASP.NET users) access to the \MSSQL\Reporting
Services\ReportServer folder (and files and subfolders), and I've granted
the IUSR_GROUP the Browser role to all reports.
So why, when using the Report Viewer web control, do I see a login box?!?|||Does anyone have any advice or suggestions here? I still haven't resolved
this.
"DJM" <msnews@.puddlestheshark.com> wrote in message
news:uLeyyLnzEHA.352@.TK2MSFTNGP14.phx.gbl...
> Ok, I've set Authentication mode="None", I've set the /ReportServer
> virtual to allow Anonymous access as IUSR, I've granted IUSR_GROUP (local
> group containing the IUSR, IWAM, and ASP.NET users) access to the
> \MSSQL\Reporting Services\ReportServer folder (and files and subfolders),
> and I've granted the IUSR_GROUP the Browser role to all reports.
> So why, when using the Report Viewer web control, do I see a login box?!?
>|||You have two options:
1. Generating the report on the server side of the application by using the
Render SOAP API. The advantage of this approach is that it is more secure
since the user doesn't see the report URL (everything takes place on the
server). The tradeoff is that the interactive features (drilldown,
drillthrough, etc.) will not work with SOAP since their require direct
access to the Report Server by URL. If you decide to take this approach, you
can pass the web app identity to the Report Server and grant a minimum set
of permissions in RS to this account.
2. Replace the RS Windows security with Forms Authentication by writing a
custom security extension. This will allow you to incorporate interactive
features in your reports. In this scenario, the reports will be requested on
the client side of the application (e.g. by using the Report Viewer sample
control). If you decide to take this approach check out the sample security
extension from MS at
(http://msdn.microsoft.com/library/?url=/library/en-us/dnsql2k/html/ufairs.a
sp?frame=true#ufairs_topic3).
So, you have to carefully weight out your requirements for security,
reporting features and your application architecture to determine the best
integration scenario.
--
Hope this helps.
Rags Iyer
"DJM" wrote:
> I'm trying to incorporate the /ReportServer virtual into our application web
> site so we can point the Report Viewer control to /ReportServer rather than
> <default web site's IP>/ReportServer. I'm trying to remove authentication
> from <app>/ReportServer, but I've been unable to keep it from popping up
> that blasted login dialog box. I've briefly tried using the FormsAuth
> sample and even rewrote it to always return True from all the authentication
> functions, but neither solved my problem.
> The application is under Forms Auth. I just want the ReportServer virtual
> to run in that context. At this point, I don't even care if it's really
> keeping authentication or just letting anyone who happens to type in
> http://<our_app>/ReportServer go uncontested. It's extremely frustrating,
> and it doesn't work for any users as it is now.
> This is SQL Server Standard, so I don't know if custom security extensions
> (assuming I really had any clue as to how they worked or how to set them up)
> would even work (I came across a page that says only Enterprise supports
> them).
>
>|||The second option would be ideal, but if you'll notice, I tried that and was
unable to get it to make a shred of difference. Maybe I'm just not smart
enough to figure it out, but it's not working for me.
"Rags Iyer" <RagsIyer@.discussions.microsoft.com> wrote in message
news:A2AD6EB1-4CE8-4305-8063-8EE6AC9E1828@.microsoft.com...
> You have two options:
> 1. Generating the report on the server side of the application by using
> the
> Render SOAP API. The advantage of this approach is that it is more secure
> since the user doesn't see the report URL (everything takes place on the
> server). The tradeoff is that the interactive features (drilldown,
> drillthrough, etc.) will not work with SOAP since their require direct
> access to the Report Server by URL. If you decide to take this approach,
> you
> can pass the web app identity to the Report Server and grant a minimum set
> of permissions in RS to this account.
> 2. Replace the RS Windows security with Forms Authentication by writing a
> custom security extension. This will allow you to incorporate interactive
> features in your reports. In this scenario, the reports will be requested
> on
> the client side of the application (e.g. by using the Report Viewer sample
> control). If you decide to take this approach check out the sample
> security
> extension from MS at
> (http://msdn.microsoft.com/library/?url=/library/en-us/dnsql2k/html/ufairs.a
> sp?frame=true#ufairs_topic3).
> So, you have to carefully weight out your requirements for security,
> reporting features and your application architecture to determine the best
> integration scenario.
> --
> Hope this helps.
> Rags Iyer
> "DJM" wrote:
>> I'm trying to incorporate the /ReportServer virtual into our application
>> web
>> site so we can point the Report Viewer control to /ReportServer rather
>> than
>> <default web site's IP>/ReportServer. I'm trying to remove
>> authentication
>> from <app>/ReportServer, but I've been unable to keep it from popping up
>> that blasted login dialog box. I've briefly tried using the FormsAuth
>> sample and even rewrote it to always return True from all the
>> authentication
>> functions, but neither solved my problem.
>> The application is under Forms Auth. I just want the ReportServer
>> virtual
>> to run in that context. At this point, I don't even care if it's really
>> keeping authentication or just letting anyone who happens to type in
>> http://<our_app>/ReportServer go uncontested. It's extremely
>> frustrating,
>> and it doesn't work for any users as it is now.
>> This is SQL Server Standard, so I don't know if custom security
>> extensions
>> (assuming I really had any clue as to how they worked or how to set them
>> up)
>> would even work (I came across a page that says only Enterprise supports
>> them).
>>
>>|||Is the Login Box still popping up when Forms Authetication is Implemented.?
"DJM" wrote:
> The second option would be ideal, but if you'll notice, I tried that and was
> unable to get it to make a shred of difference. Maybe I'm just not smart
> enough to figure it out, but it's not working for me.
> "Rags Iyer" <RagsIyer@.discussions.microsoft.com> wrote in message
> news:A2AD6EB1-4CE8-4305-8063-8EE6AC9E1828@.microsoft.com...
> > You have two options:
> >
> > 1. Generating the report on the server side of the application by using
> > the
> > Render SOAP API. The advantage of this approach is that it is more secure
> > since the user doesn't see the report URL (everything takes place on the
> > server). The tradeoff is that the interactive features (drilldown,
> > drillthrough, etc.) will not work with SOAP since their require direct
> > access to the Report Server by URL. If you decide to take this approach,
> > you
> > can pass the web app identity to the Report Server and grant a minimum set
> > of permissions in RS to this account.
> >
> > 2. Replace the RS Windows security with Forms Authentication by writing a
> > custom security extension. This will allow you to incorporate interactive
> > features in your reports. In this scenario, the reports will be requested
> > on
> > the client side of the application (e.g. by using the Report Viewer sample
> > control). If you decide to take this approach check out the sample
> > security
> > extension from MS at
> > (http://msdn.microsoft.com/library/?url=/library/en-us/dnsql2k/html/ufairs.a
> > sp?frame=true#ufairs_topic3).
> >
> > So, you have to carefully weight out your requirements for security,
> > reporting features and your application architecture to determine the best
> > integration scenario.
> > --
> > Hope this helps.
> >
> > Rags Iyer
> >
> > "DJM" wrote:
> >
> >> I'm trying to incorporate the /ReportServer virtual into our application
> >> web
> >> site so we can point the Report Viewer control to /ReportServer rather
> >> than
> >> <default web site's IP>/ReportServer. I'm trying to remove
> >> authentication
> >> from <app>/ReportServer, but I've been unable to keep it from popping up
> >> that blasted login dialog box. I've briefly tried using the FormsAuth
> >> sample and even rewrote it to always return True from all the
> >> authentication
> >> functions, but neither solved my problem.
> >>
> >> The application is under Forms Auth. I just want the ReportServer
> >> virtual
> >> to run in that context. At this point, I don't even care if it's really
> >> keeping authentication or just letting anyone who happens to type in
> >> http://<our_app>/ReportServer go uncontested. It's extremely
> >> frustrating,
> >> and it doesn't work for any users as it is now.
> >>
> >> This is SQL Server Standard, so I don't know if custom security
> >> extensions
> >> (assuming I really had any clue as to how they worked or how to set them
> >> up)
> >> would even work (I came across a page that says only Enterprise supports
> >> them).
> >>
> >>
> >>
> >>
>
>|||Yes.
"Rags Iyer" <RagsIyer@.discussions.microsoft.com> wrote in message
news:C574F74E-C580-47A4-86AD-BCD62253C700@.microsoft.com...
> Is the Login Box still popping up when Forms Authetication is
> Implemented.?|||Please check wherther the Security implemenation for Forms Authetication was
properly implemented.The authetication in the Rs Config File needs to be
changed to Forms Authentication and all the required policy is set.
Regards,
Rags Iyer
"DJM" wrote:
> Yes.
> "Rags Iyer" <RagsIyer@.discussions.microsoft.com> wrote in message
> news:C574F74E-C580-47A4-86AD-BCD62253C700@.microsoft.com...
> >
> > Is the Login Box still popping up when Forms Authetication is
> > Implemented.?
>
>|||Please check wherther the Security implemenation for Forms Authetication was
properly implemented.The authetication in the Rs Config File needs to be
changed to Forms Authentication and all the required policy is set.
Regards,
Rags Iyer
"DJM" wrote:
> Yes.
> "Rags Iyer" <RagsIyer@.discussions.microsoft.com> wrote in message
> news:C574F74E-C580-47A4-86AD-BCD62253C700@.microsoft.com...
> >
> > Is the Login Box still popping up when Forms Authetication is
> > Implemented.?
>
>|||I did that according to the documentation (adding Forms to the
authentication types or wherever that is, and changing authentication mode
to Forms in the web.config), and I was still getting the login box.
What gets me is that box is still appearing even when I set the
authentication mode to None.
"Rags Iyer" <RagsIyer@.discussions.microsoft.com> wrote in message
news:E5169863-A011-43A4-BAB3-A0627C0A0272@.microsoft.com...
> Please check wherther the Security implemenation for Forms Authetication
> was
> properly implemented.The authetication in the Rs Config File needs to be
> changed to Forms Authentication and all the required policy is set.
> Regards,
> Rags Iyer
> "DJM" wrote:
>> Yes.
>> "Rags Iyer" <RagsIyer@.discussions.microsoft.com> wrote in message
>> news:C574F74E-C580-47A4-86AD-BCD62253C700@.microsoft.com...
>> >
>> > Is the Login Box still popping up when Forms Authetication is
>> > Implemented.?
>>

Make SQL Agent use drive mapping?

Good day,
I'm migrating our current SQL 2k box (running on win 2000) to a new Windows 2003 server. I'm having trouble getting the SQL agent to use the servers drive mapping when running jobs. The odbc driver that I'm using does not support UNC paths. I know, dri
ve mapping are not cool becuase we have to keep the server logged in but it's the only way and it does work on our old box. The weird thing is that I can't get this working on the new server. On the old box the SQL Agent is set to run as the same accoun
t as the logged in user and it can access the drive mappings fine, it's been running this way for quite some time. However, on my new box this does not work...is this a windows 2003 server thing? I'm runing SQL 2k SP3 on both boxes. Also, the new box i
n not in a domain so the account I'm trying to use is a local admin acount.
Any ideas?
Drive mappings are not guaranteed to work when being accessed from a
service. There is no way to force them to work.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I figured it out. I simply added a step in each scheduled job to create and then delete the drive mapping.
For example, I just use the "net use f: \\server\volume" to create the drive ampping an then excute the rest of my job steps and then use another step with this command "net use f: /delete" to delete it. Becuase the SQL Agent service is excuting the comm
and the drive mapping is in it's session and it works every time. It's nice becuase the drive mapping isn't even seen by the desktop and works when the server in not logged in. I remove the drive mapping at the end of each job becuase the drive mapping
remains in tack as long as the SQL agent service stays running and therefore if another job runs and tries to re-create the drive mapping the job will fail.

Make SQL Agent use drive mapping?

Good day,
I'm migrating our current SQL 2k box (running on win 2000) to a new Windows
2003 server. I'm having trouble getting the SQL agent to use the servers dr
ive mapping when running jobs. The odbc driver that I'm using does not supp
ort UNC paths. I know, dri
ve mapping are not cool becuase we have to keep the server logged in but it'
s the only way and it does work on our old box. The weird thing is that I c
an't get this working on the new server. On the old box the SQL Agent is se
t to run as the same accoun
t as the logged in user and it can access the drive mappings fine, it's been
running this way for quite some time. However, on my new box this does not
work...is this a windows 2003 server thing? I'm runing SQL 2k SP3 on both
boxes. Also, the new box i
n not in a domain so the account I'm trying to use is a local admin acount.
Any ideas?Drive mappings are not guaranteed to work when being accessed from a
service. There is no way to force them to work.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I figured it out. I simply added a step in each scheduled job to create and
then delete the drive mapping.
For example, I just use the "net use f: \\server\volume" to create the drive
ampping an then excute the rest of my job steps and then use another step w
ith this command "net use f: /delete" to delete it. Becuase the SQL Agent s
ervice is excuting the comm
and the drive mapping is in it's session and it works every time. It's nice
becuase the drive mapping isn't even seen by the desktop and works when the
server in not logged in. I remove the drive mapping at the end of each job
becuase the drive mapping
remains in tack as long as the SQL agent service stays running and therefore
if another job runs and tries to re-create the drive mapping the job will f
ail.

Make a list box not reqired.

I have a report that takes values from a list box to generate the report.
The list box gets its values from a table.
If the user does not coose anything from the list box and hits 'View Report'
It should be able to go and grab all data from the table.
How do I make RS do this?
I tried 'Allow Null Value' for that particular parameter, but it still does
not work.
Anyone knows how to do this?You could grap the value "%" as a default value of this list box and put it
in your query, nevertheless if you are usinga stored procedure you can
handle the "empty" paramters, or you use the ISNULL(Parameter,Value) in your
query. Today it´s kind of a hack to do this ;-)
HTH, Jens Süßmeyer.
--
http://www.sqlserver2005.de
--
"appu" <appu@.discussions.microsoft.com> schrieb im Newsbeitrag
news:6E985A61-49F3-4AE1-B504-29E0954EA649@.microsoft.com...
>I have a report that takes values from a list box to generate the report.
> The list box gets its values from a table.
> If the user does not coose anything from the list box and hits 'View
> Report'
> It should be able to go and grab all data from the table.
> How do I make RS do this?
> I tried 'Allow Null Value' for that particular parameter, but it still
> does
> not work.
> Anyone knows how to do this?|||Thanks! I got the answer.
I can do a union of 'all', '<select all>'
when I grab my parameters from the table.
"Jens Sü�meyer" wrote:
> You could grap the value "%" as a default value of this list box and put it
> in your query, nevertheless if you are usinga stored procedure you can
> handle the "empty" paramters, or you use the ISNULL(Parameter,Value) in your
> query. Today it´s kind of a hack to do this ;-)
> HTH, Jens Sü�meyer.
> --
> http://www.sqlserver2005.de
> --
> "appu" <appu@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:6E985A61-49F3-4AE1-B504-29E0954EA649@.microsoft.com...
> >I have a report that takes values from a list box to generate the report.
> > The list box gets its values from a table.
> > If the user does not coose anything from the list box and hits 'View
> > Report'
> > It should be able to go and grab all data from the table.
> > How do I make RS do this?
> > I tried 'Allow Null Value' for that particular parameter, but it still
> > does
> > not work.
> > Anyone knows how to do this?
>
>

Maintenance Plans won't allow me to select to delete jobs after 3 days

SQL Server 2000 (SP3A) won't allow me to select to delete any jobs older tha
n 3 days. I don't get the option in the drop down box. When I change to 3
it goes back to 0 and again no option in the drop down box.
I manually went in to job (steps tab) and inserted DAYS next to the 3 and ra
n a sql backup job after this to see if it would delete the jobs older than
3 days. It didn't delete any of them. This is occurring on both the .bak a
nd .trn files, however on t
he reports it is allowing me to select both number of days and days themselv
e. (currently set to 5 days)
This is frustrating as we are now manually deleting jobs so they don't run o
ut of hard drive space when performining nightly backup and maintenance on t
he sql server.
Any help is greatly appreciated. Permissions have been checked etc and ever
ything appears to be accurate.did you try to purge backup files or jobs older than 3 days?
1. maintenance plan will purge backup or trans log backup files after
certain days if you spcify it.
2. it does not purge jobs!
3. why would you create a job then purge it 3 days later?
Steve
"Sheri" <sheri@.isdesign.com> wrote in message
news:F868C089-CDF3-4F25-B750-6227AEBFEE12@.microsoft.com...
> SQL Server 2000 (SP3A) won't allow me to select to delete any jobs older
than 3 days. I don't get the option in the drop down box. When I change to
3 it goes back to 0 and again no option in the drop down box.
> I manually went in to job (steps tab) and inserted DAYS next to the 3 and
ran a sql backup job after this to see if it would delete the jobs older
than 3 days. It didn't delete any of them. This is occurring on both the
.bak and .trn files, however on the reports it is allowing me to select bot
h
number of days and days themselve. (currently set to 5 days)
> This is frustrating as we are now manually deleting jobs so they don't run
out of hard drive space when performining nightly backup and maintenance on
the sql server.
> Any help is greatly appreciated. Permissions have been checked etc and
everything appears to be accurate.
>

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.
======================================================

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 databas
es
> to backup. I see AdventureWorks, AdventureWorksSW, master, model and msdb.
> Object Explorer doesn't show "msdb". Maybe it is my DB ? Strange because m
y
> 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/subscript...ault.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/subscript...t/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/subscript...ault.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/subscript...t/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 mes
sage
de news:x9I%234XGbHHA.928@.TK2MSFTNGHUB02.phx.gbl...
> Hi,
> For your three questions, please see the following answers:
> and
> 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?
>
change[vbcol=seagreen]
> can
> 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.
>
> backup,
> 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/subscript...ault.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/subscript...t/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/subscript...ault.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/subscript...t/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.
========================================
==============