Help Files / Metadata on Reports

I had a pervious thread on a metadata KB but didn't get a response. So I was wondering if anyone has added on a web based help file app to SSRS? Something that you could assign additional metadata to each report. Something that would be searchable.

At this point SSRS doesn't provide enough fields for metadata. I am looking to assign some thing like:

1. Owner/Requestor of report

2. Fields in report

3. Description (other than the one provided)

4. etc..

Does anyone have any ideas of a add on, utility, or software?

Thanks

fsugeiger

Hmmm...I'm not sure I understand what you're asking for, but couldn't you create a report on reports?

In other words, store in your database information about reports, then create a report out of it.

|||Yes, i thought of that but I would have to create a table of report fields and parameters. I didn't want to have to maintain something seperate. i wanted something to read the rdl file and list fields and parameters.

Help Files / Metadata on Reports

I had a pervious thread on a metadata KB but didn't get a response. So I was wondering if anyone has added on a web based help file app to SSRS? Something that you could assign additional metadata to each report. Something that would be searchable.

At this point SSRS doesn't provide enough fields for metadata. I am looking to assign some thing like:

1. Owner/Requestor of report

2. Fields in report

3. Description (other than the one provided)

4. etc..

Does anyone have any ideas of a add on, utility, or software?

Thanks

fsugeiger

Hmmm...I'm not sure I understand what you're asking for, but couldn't you create a report on reports?

In other words, store in your database information about reports, then create a report out of it.

|||Yes, i thought of that but I would have to create a table of report fields and parameters. I didn't want to have to maintain something seperate. i wanted something to read the rdl file and list fields and parameters.sql

Help Designing an App. to be Run from a Job

Hello,

I'm working on a project that uses SQL Server 2005 and C# 2.0. I need some ideas of the best way to design/implement an application that will be executed from a SQL Server job.

The general idea is: a SQL Server job will call [something] and pass a couple of parameters to [something], then [something] will query a database and gather other information, then [something] will do some processing of data, and finally [something] will output the results for end user consumption.

The problem is that I don't know what [something] should be. Should it be a C# executable (but it can have no UI)? Should it be a web service? Should it be a console application (but, again, it cannot have a UI)? Should the job call a stored procedure, which in turn calls a C# assembly?

Basically, I'm just trying to get some ideas of the best way to design/implement a solution to my situation.

Thanks.

Hi,

without further information, I would suggest to use a c# console app called from the job.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

Thanks for the input.

What other information could I provide to help choose the best solution?

|||

Best thing is to call a Stored Proc from the Sql job

In the Stored proc gather all the parameters that you need and use BCP out to keep that data in a flat file.

There is no need to use Webservice or other C# program as this would cause an additional overhead.

|||

There are a number of things your description suggests, and others that it leaves open...

1 - from what you say, it looks like the something does not need access to the resources of the server (as a computer) and only needs access to data inside SQL Server. If this is true, then the use of a SQL Server job to invoke a stored procedure is the way to go (and in SQL Server 2005 you can write your stored procedure in C# if you like).

If, on the other hand, you need access to information outside SQL Server (files, I/O, Active Directory, other PCs, ...) you'll need an app running outside SQL Server (yes - you can invoke an app from inside SQL Server, but why jump through hoops when you don't need to?). If this is the road to take, use Windows' scheduler instead of SQL Server's scheduler.

If you're running inside SQL Server, as one of the other posts suggested, you'll have a Stored Proc to gather parameters, that likely will call another (or more) to do the work. If you're doing stuff outside the database server the app will likely invoke a stored proc to do the 'inside' work - so you're just partitioning where you do what work.

When returning the data to the user - there are a number of options that depend on various factors you've not mentioned as to which is better:

> simply write the data to an output table (with a timestamp on each row if you need to hold multiple day's / run's worth of output) - and the use can have a simple reporting app to read from it.

> If the volume of data is small SQL Server can email the recipient(s) - again, this is probably better if the number of recipients is small. You may also need to consider the security of the data as it travels as email.

> If you need to store the data outside the server (in a dated file, for example) you have to get it out, somehow. If your app is already running outside the server that's a no brainer; if everything is running inside the server I think you'll have to trigger some outside app to pull the data (i.e. I don't think there's a way for a SQL Server job to dump data to the outside world). DO NOT TAKE MY WORD for this - DTS may be invokable as a SQL Server job and may server to store data outside the server, or there may be other capabilities of SQL Server 2005 that I've not encountered yet.

> Worst comes to worst - you have a simple outside app that polls a table in the server for a 'ready' flag and then pulls the data. But that's ugly.

HTH

Griffin

sql

Help - Sql Server 2005 at a crawl on Win 2000 Server

Hello -
I know nothing about running servers, however, I am in a position where I
not only programmed the app, programmed Sql Server 2005 for the app and but
now had to install Sql Server 2005 on a box that was given to me - Pentium I
V
with 40 gigs of storage and 512 MB RAM. I thought the machine would be
sufficient, however, it has been running (with no users using the app yet)
for three days and it's at a crawl. The OS is Windows 2000 Server.
Any suggestions as to what may a likely problem? (Looks like some kind of
memory leak to me.) I know more specifics are probably needed, but I don't
know what specifics to provide.
Any help will be greatly appreciated! These people expect this app to be up
and running by Thursday morning!!!!
--
SandySandy
http://www.microsoft.com/sql/prodin...qs/default.mspx
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:AA02BFDD-1790-4A30-BA64-DE8937B5172A@.microsoft.com...
> Hello -
> I know nothing about running servers, however, I am in a position where I
> not only programmed the app, programmed Sql Server 2005 for the app and
> but
> now had to install Sql Server 2005 on a box that was given to me - Pentium
> IV
> with 40 gigs of storage and 512 MB RAM. I thought the machine would be
> sufficient, however, it has been running (with no users using the app yet)
> for three days and it's at a crawl. The OS is Windows 2000 Server.
> Any suggestions as to what may a likely problem? (Looks like some kind of
> memory leak to me.) I know more specifics are probably needed, but I
> don't
> know what specifics to provide.
> Any help will be greatly appreciated! These people expect this app to be
> up
> and running by Thursday morning!!!!
> --
> Sandy|||Apart from what Uri has recommended - particuarly the bit about 1GB memory
recommended, there are a number of measurements you could take focusing
around CPU,RAM,Hard Disk . I haven't included Network as it sounds like
there are no users, which is the main cause for network bottlenecks.
Quick tests are: Pages/Sec memory, percentage disk time, average disk queue
length , buffer cache hit ratio .
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
___________________________________
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:AA02BFDD-1790-4A30-BA64-DE8937B5172A@.microsoft.com...
> Hello -
> I know nothing about running servers, however, I am in a position where I
> not only programmed the app, programmed Sql Server 2005 for the app and
but
> now had to install Sql Server 2005 on a box that was given to me - Pentium
IV
> with 40 gigs of storage and 512 MB RAM. I thought the machine would be
> sufficient, however, it has been running (with no users using the app yet)
> for three days and it's at a crawl. The OS is Windows 2000 Server.
> Any suggestions as to what may a likely problem? (Looks like some kind of
> memory leak to me.) I know more specifics are probably needed, but I
don't
> know what specifics to provide.
> Any help will be greatly appreciated! These people expect this app to be
up
> and running by Thursday morning!!!!
> --
> Sandy|||Hi Jack and Uri -
Thank you very much for your responses.
One further question: I looked through the System properties and noticed
that under Performance Options (System Properties -> Advanced -> Performance
Options - Optimize Performance), "Background" is checked. Should
"Applications" be checked there instead?
Again, any help will be greatly appreciated!
--
Sandy
"Sandy" wrote:

> Hello -
> I know nothing about running servers, however, I am in a position where I
> not only programmed the app, programmed Sql Server 2005 for the app and bu
t
> now had to install Sql Server 2005 on a box that was given to me - Pentium
IV
> with 40 gigs of storage and 512 MB RAM. I thought the machine would be
> sufficient, however, it has been running (with no users using the app yet)
> for three days and it's at a crawl. The OS is Windows 2000 Server.
> Any suggestions as to what may a likely problem? (Looks like some kind of
> memory leak to me.) I know more specifics are probably needed, but I don'
t
> know what specifics to provide.
> Any help will be greatly appreciated! These people expect this app to be
up
> and running by Thursday morning!!!!
> --
> Sandy

Help

I've just learned an asp.net 2.0 web app with vs 2005 and am using a SQL Server 2005. But after running programme the error occur.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

please help me! Fix it

Enable remote connections at the SQL Server. http://www.sqlserver2005.de/SharedFiles/remoteconnection.jpg

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

|||

I have finished the remote connection but my program not running. it still inform error:

Server Error in '/TipcGiaLai' Application.

---

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Source Error:

Line 11: conPubs = New SqlConnection( "Server=localhost;UID=;PWD=;Database=Pubs" )

Line 12: cmdSelect = New SqlCommand( "Select * From Authors", conPubs )

Line 13: conPubs.Open()

Line 14: dtrAuthors = cmdSelect.ExecuteReader()

Line 15:

please help me ! Thanks

Help

I've just learned an asp.net 2.0 web app with vs 2005 and am using a SQL Server 2005. But after running programme the error occur.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

please help me! Fix it

Enable remote connections at the SQL Server. http://www.sqlserver2005.de/SharedFiles/remoteconnection.jpg

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

|||

I have finished the remote connection but my program not running. it still inform error:

Server Error in '/TipcGiaLai' Application.

---

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Source Error:

Line 11: conPubs = New SqlConnection( "Server=localhost;UID=;PWD=;Database=Pubs" ) Line 12: cmdSelect = New SqlCommand( "Select * From Authors", conPubs ) Line 13: conPubs.Open() Line 14: dtrAuthors = cmdSelect.ExecuteReader() Line 15:

please help me ! Thanks