New to Reporting Services

We have a license for SQL Server Enterprise.The license is per processor.We plan to use Reporting Services. I was wondering if there is going to be a limitation for the number of the users that can use this. Similar with Crystal asking for license for more than 5 concurrent users.
We'll access Reporting Services from a web site.Unfortunately the web site is plain ASP.Is there any way I can use Reporting Service(maybe the web service) from plain ASP, or should I think about a way to integrate an ASP.NET page?
The report is generated based on some data the users are entering, and is not related in any way to any database, can I push some xml from my page to the Reporting Service?
Do I need to have a SSL certificate to use Reporting Services?
Can I just download Reporting Services from Microsoft, or is it available only on a CD? We are somehow in a hurry, I don't have too much time to wait for CD's.
Thanks,
IoanaThe requirements for SQL Server Reporting Services are listed herehttp://www.microsoft.com/sql/reporting/productinfo/sysreqs.mspx you will see that the server needs the .NET framework. When that is setup ASP applications should be able to call the reports with a URL or you can use the web service that is part of it.
To my knowledge there is no limit for the number of concurrent Reporting Services users.
An SSL certificate isn't essential but is advisable.
You can download the demonstration which should get you going until you get the CD
Steve|||Thank you Steve.That answers all my questions.:o)

New database not included in "Back Up Database Task"

I'm having a problem with a Maintenance Plan created for SQL Server 2005 using Microsoft SQL Server Management Studio. See version information at the bottom of this post.

I have a Maintenance Plan using the "Back Up Database Task" that is set to perform a "Full" back up of "All Databases" on the local server. However, it appears that the list of "All databases" are hard-coded to be those databases that were available at the time the task was created. It seems any newly created databases don't appear to be in the list. If I attempt to edit the task and select the "These databases:" option, the newly created databases aren't even in the list.

Is there some way to have the task refresh the list of the databases available for backup? Ideally, I'd like any newly created databases to get backed up automatically without having to modify the task.

Thanks for your help,

Jonathan.

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
Microsoft MSXML 2.6 3.0 4.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

Hi,

I tested this on a SQL SP2 build 3175 and could not reproduce the issue.

Any newly added database automatically shows-up in the list.

I advise to patch and re-test.

Regards,

Philippe

|||After doing further tests, I determined that not all newly created databases are excluded from the backup. However, it appears that databases that were created on this SQL Server 2005 database and then had data restored from a .bak file from a SQL Server 7 database server are being excluded. I'm guessing it's a permission problem.

Can someone tell me exactly what users and/or roles need to be added to my databases in order for them to be backed up via the "Back UP Database Task"? Alternatively, if there's another non-permission solution, please let me know.

Thanks,

Jonathan.

|||

You must change the compatibility mode of your Database to SQL server 2005 this way it will allow all the features of SQL server 2005 to be used.... such as the backup.

Cheers

Byblyk

|||

Yep, that does it. For any others that run into the same problem and need a bit more handholding, open up "SQL Server Management Studio". Under "Databases", select right click your database and select "Properties". Under the "Options" page, set the "Compatability level" to "SQL Server 2005 (90)".

Note, it's important to make sure you check what changes to the compatability level mean before setting them willy nilly. Here's a useful guide:

http://msdn2.microsoft.com/en-us/library/ms178653.aspx

Thanks Byblyk!

New database not included in "Back Up Database Task"

I'm having a problem with a Maintenance Plan created for SQL Server 2005 using Microsoft SQL Server Management Studio. See version information at the bottom of this post.

I have a Maintenance Plan using the "Back Up Database Task" that is set to perform a "Full" back up of "All Databases" on the local server. However, it appears that the list of "All databases" are hard-coded to be those databases that were available at the time the task was created. It seems any newly created databases don't appear to be in the list. If I attempt to edit the task and select the "These databases:" option, the newly created databases aren't even in the list.

Is there some way to have the task refresh the list of the databases available for backup? Ideally, I'd like any newly created databases to get backed up automatically without having to modify the task.

Thanks for your help,

Jonathan.

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
Microsoft MSXML 2.6 3.0 4.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

Hi,

I tested this on a SQL SP2 build 3175 and could not reproduce the issue.

Any newly added database automatically shows-up in the list.

I advise to patch and re-test.

Regards,

Philippe

|||After doing further tests, I determined that not all newly created databases are excluded from the backup. However, it appears that databases that were created on this SQL Server 2005 database and then had data restored from a .bak file from a SQL Server 7 database server are being excluded. I'm guessing it's a permission problem.

Can someone tell me exactly what users and/or roles need to be added to my databases in order for them to be backed up via the "Back UP Database Task"? Alternatively, if there's another non-permission solution, please let me know.

Thanks,

Jonathan.

|||

You must change the compatibility mode of your Database to SQL server 2005 this way it will allow all the features of SQL server 2005 to be used.... such as the backup.

Cheers

Byblyk

|||

Yep, that does it. For any others that run into the same problem and need a bit more handholding, open up "SQL Server Management Studio". Under "Databases", select right click your database and select "Properties". Under the "Options" page, set the "Compatability level" to "SQL Server 2005 (90)".

Note, it's important to make sure you check what changes to the compatability level mean before setting them willy nilly. Here's a useful guide:

http://msdn2.microsoft.com/en-us/library/ms178653.aspx

Thanks Byblyk!

New database not included in "Back Up Database Task"

I'm having a problem with a Maintenance Plan created for SQL Server 2005 using Microsoft SQL Server Management Studio. See version information at the bottom of this post.

I have a Maintenance Plan using the "Back Up Database Task" that is set to perform a "Full" back up of "All Databases" on the local server. However, it appears that the list of "All databases" are hard-coded to be those databases that were available at the time the task was created. It seems any newly created databases don't appear to be in the list. If I attempt to edit the task and select the "These databases:" option, the newly created databases aren't even in the list.

Is there some way to have the task refresh the list of the databases available for backup? Ideally, I'd like any newly created databases to get backed up automatically without having to modify the task.

Thanks for your help,

Jonathan.

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
Microsoft MSXML 2.6 3.0 4.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

Hi,

I tested this on a SQL SP2 build 3175 and could not reproduce the issue.

Any newly added database automatically shows-up in the list.

I advise to patch and re-test.

Regards,

Philippe

|||After doing further tests, I determined that not all newly created databases are excluded from the backup. However, it appears that databases that were created on this SQL Server 2005 database and then had data restored from a .bak file from a SQL Server 7 database server are being excluded. I'm guessing it's a permission problem.

Can someone tell me exactly what users and/or roles need to be added to my databases in order for them to be backed up via the "Back UP Database Task"? Alternatively, if there's another non-permission solution, please let me know.

Thanks,

Jonathan.

|||

You must change the compatibility mode of your Database to SQL server 2005 this way it will allow all the features of SQL server 2005 to be used.... such as the backup.

Cheers

Byblyk

|||

Yep, that does it. For any others that run into the same problem and need a bit more handholding, open up "SQL Server Management Studio". Under "Databases", select right click your database and select "Properties". Under the "Options" page, set the "Compatability level" to "SQL Server 2005 (90)".

Note, it's important to make sure you check what changes to the compatability level mean before setting them willy nilly. Here's a useful guide:

http://msdn2.microsoft.com/en-us/library/ms178653.aspx

Thanks Byblyk!

New CTP

Will there be an August CTP of Sql Server 2005?

What interim version do you still plan on releasing before RTM on November 7th?

Hi,

in the internet I read something about a beta 3.

|||Beta 3 was another name for the June CTP (which doesn't work on DCs!), Microsoft announced that they would only create CTP's before the final release... So I really hope we can expect one soon, if only to test if everything works correctly now on domain controllers...

Can someone from Microsoft please give us an update?|||

I can say that we're discussing releasing another CTP prior to RTM but I can't say for certain if this will happen and if it does when. Sorry for being so vague.

Dan