Talk:SQL Server Reporting Services

Comparison of Reporting Services
I've added several links to some alternatives quickly to ensure a balanced article but these alternatives need adding to and my thoughts are on the migration to a full page on reporting services options with comparison charts. Otherwise this article sits far too much on its own and focuses entirely on SSRS. Providing alternatives is a temporary solution. Genericprodigy (talk) 09:25, 17 July 2008 (UTC)
 * You've singled out "Crystal Reports" and then just thrown everything else under the banner of "others". The placing of that in the first paragraph of the article looks highly suspect.   I'd suggest putting references to other products further down the article in a place with less prominence,  so they look less like product placement. This article is supposed to be about SSRS, not and advertising platform for Crystal Reports  (talk) 09:08, 14 November 2019 (GMT) — Preceding comment signed as by Johnboyjimmyfly (talk· contribs)  actually added by 217.38.34.2 (talk·contribs)

General thoughts
This page is quite lacking for something that is really starting to gain traction. I'll try to spend some time on it if I can. I have begun by added a few links that explain how people can integrate SSRS with their Java applications, etc. 81.134.144.135 (talk) 17:20, 18 April 2011 (UTC)
 * Wikipedia is not a manual. An article about software should explain its history, general applications, and relationship to other software, but it's not necessary (and possibly even harmful) to attempt to provide a user guide. Ibadibam (talk) 22:36, 15 November 2019 (UTC)

Opening Paragraph
It is administered via a web interface. Reporting services features a web services interface to support the development of custom reporting applications.

These two sentences say the same thing in different ways. — Preceding unsigned comment added by 75.59.221.42 (talk) 19:49, 31 October 2011 (UTC)

Paragraph in "Use" section
This paragraph seems strangely written to me, with some grammatical errors too. I think it could certainly do with a rewrite by someone more knowledgeable on the subject than me.

''Typically the reports are only revealed to users able to run them, and SQL connections in the source allow anyone to run with sufficient privileges. This is because configuring Windows Authentication through the reports execution is laborious and time consuming: a Server Principal Name record (requiring DOMAIN ADMINISTRATOR access) is created in Active Directory associating the Sql Server Reporting service to the user the service runs under on the server (a network user to facilitate querying the Active Directory)... and the service account user has to have the delegation option enabled, the server must be trusted for delegation too; the windows users wishing to run reports must be set to allow delegation - so Kerberos authentication protocols will be used. The reporting service itself has to have the configuration edited to enable Kerberos protocols... but then the reports will be secure and only display data the individual users are permitted to (based on SQL security configuration).''

165.225.81.41 (talk) 15:10, 20 December 2019 (UTC)