INFO: Reporting Web Server stopped

I see an this message at the end of the the
ReportServer__mm_dd_yy_hh_mm_ss.log file the second oldest log file.
w3wp!webserver!1!11/28/2007-09:17:57:: i INFO: Reporting Web
Server stopped
Then in the most recent log file I see this at the beginning:
w3wp!webserver!9!11/28/2007-10:37:19:: i INFO: Reporting Web Server
started
I assume this is because I have some how set up reporting to services to
automatically shutdown after a period of non-activity.
It seems that everytime the first person tries reporting services when it is
stopped. It takes a long time to render the report. Then after it is
running it gets rendered much quicker. Once again I'm guessing this happens
be cause reporting services needs to start (slow rendering), or is all ready
running (fast rendering).
Is ther way to always keep the Reporting Web Server running and not having
is shut down periodically Are there drawbacks to doing this?
--
If you are looking for SQL Server examples or a free SQL Server DBA
Dashboard tool check out my Website at http://www.sqlserverexamples.comThis is an IIS issue.
Go to IIS Manager, under Applocation Pools node, right click
"DefaultAppPool" in which the Reporting Server work process is running,
select properties. On "Performace" tag, you will see, by default, the app
pool will shut down if > being idle for 20 min. You can extend this time to
8x60min 480min, so that the app pool will not shut down for a regular
working day. However, the first report reader of the day, will hit the
delay. You may schedule a dummy report at beginning of a work day for this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Greg Larsen" <gregalarsen@.removeit.msn.com> wrote in message
news:F30BE481-A090-4988-B5B4-8D3A44B64627@.microsoft.com...
>I see an this message at the end of the the
> ReportServer__mm_dd_yy_hh_mm_ss.log file the second oldest log file.
> w3wp!webserver!1!11/28/2007-09:17:57:: i INFO: Reporting Web
> Server stopped
> Then in the most recent log file I see this at the beginning:
> w3wp!webserver!9!11/28/2007-10:37:19:: i INFO: Reporting Web
> Server
> started
> I assume this is because I have some how set up reporting to services to
> automatically shutdown after a period of non-activity.
> It seems that everytime the first person tries reporting services when it
> is
> stopped. It takes a long time to render the report. Then after it is
> running it gets rendered much quicker. Once again I'm guessing this
> happens
> be cause reporting services needs to start (slow rendering), or is all
> ready
> running (fast rendering).
> Is ther way to always keep the Reporting Web Server running and not having
> is shut down periodically Are there drawbacks to doing this?
>
> --
> If you are looking for SQL Server examples or a free SQL Server DBA
> Dashboard tool check out my Website at http://www.sqlserverexamples.com|||I just unchecked the box. Doesn't unchecking the box in the performance tab
disable the non-activity shutdown all together?
--
If you are looking for SQL Server examples or a free SQL Server DBA
Dashboard tool check out my Website at http://www.sqlserverexamples.com
"Bruce L-C [MVP]" wrote:
> This is an IIS issue.
> Go to IIS Manager, under Applocation Pools node, right click
> "DefaultAppPool" in which the Reporting Server work process is running,
> select properties. On "Performace" tag, you will see, by default, the app
> pool will shut down if > being idle for 20 min. You can extend this time to
> 8x60min 480min, so that the app pool will not shut down for a regular
> working day. However, the first report reader of the day, will hit the
> delay. You may schedule a dummy report at beginning of a work day for this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Greg Larsen" <gregalarsen@.removeit.msn.com> wrote in message
> news:F30BE481-A090-4988-B5B4-8D3A44B64627@.microsoft.com...
> >I see an this message at the end of the the
> > ReportServer__mm_dd_yy_hh_mm_ss.log file the second oldest log file.
> >
> > w3wp!webserver!1!11/28/2007-09:17:57:: i INFO: Reporting Web
> > Server stopped
> >
> > Then in the most recent log file I see this at the beginning:
> >
> > w3wp!webserver!9!11/28/2007-10:37:19:: i INFO: Reporting Web
> > Server
> > started
> >
> > I assume this is because I have some how set up reporting to services to
> > automatically shutdown after a period of non-activity.
> >
> > It seems that everytime the first person tries reporting services when it
> > is
> > stopped. It takes a long time to render the report. Then after it is
> > running it gets rendered much quicker. Once again I'm guessing this
> > happens
> > be cause reporting services needs to start (slow rendering), or is all
> > ready
> > running (fast rendering).
> >
> > Is ther way to always keep the Reporting Web Server running and not having
> > is shut down periodically Are there drawbacks to doing this?
> >
> >
> > --
> > If you are looking for SQL Server examples or a free SQL Server DBA
> > Dashboard tool check out my Website at http://www.sqlserverexamples.com
>
>|||I don't think so. I think it just does the default.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Greg Larsen" <gregalarsen@.removeit.msn.com> wrote in message
news:8A7FABB3-0295-4C42-BBF5-889A53B63AFB@.microsoft.com...
>I just unchecked the box. Doesn't unchecking the box in the performance
>tab
> disable the non-activity shutdown all together?
> --
> If you are looking for SQL Server examples or a free SQL Server DBA
> Dashboard tool check out my Website at http://www.sqlserverexamples.com
>
> "Bruce L-C [MVP]" wrote:
>> This is an IIS issue.
>> Go to IIS Manager, under Applocation Pools node, right click
>> "DefaultAppPool" in which the Reporting Server work process is running,
>> select properties. On "Performace" tag, you will see, by default, the
>> app
>> pool will shut down if > being idle for 20 min. You can extend this time
>> to
>> 8x60min 480min, so that the app pool will not shut down for a regular
>> working day. However, the first report reader of the day, will hit the
>> delay. You may schedule a dummy report at beginning of a work day for
>> this.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Greg Larsen" <gregalarsen@.removeit.msn.com> wrote in message
>> news:F30BE481-A090-4988-B5B4-8D3A44B64627@.microsoft.com...
>> >I see an this message at the end of the the
>> > ReportServer__mm_dd_yy_hh_mm_ss.log file the second oldest log file.
>> >
>> > w3wp!webserver!1!11/28/2007-09:17:57:: i INFO: Reporting Web
>> > Server stopped
>> >
>> > Then in the most recent log file I see this at the beginning:
>> >
>> > w3wp!webserver!9!11/28/2007-10:37:19:: i INFO: Reporting Web
>> > Server
>> > started
>> >
>> > I assume this is because I have some how set up reporting to services
>> > to
>> > automatically shutdown after a period of non-activity.
>> >
>> > It seems that everytime the first person tries reporting services when
>> > it
>> > is
>> > stopped. It takes a long time to render the report. Then after it is
>> > running it gets rendered much quicker. Once again I'm guessing this
>> > happens
>> > be cause reporting services needs to start (slow rendering), or is all
>> > ready
>> > running (fast rendering).
>> >
>> > Is ther way to always keep the Reporting Web Server running and not
>> > having
>> > is shut down periodically Are there drawbacks to doing this?
>> >
>> >
>> > --
>> > If you are looking for SQL Server examples or a free SQL Server DBA
>> > Dashboard tool check out my Website at http://www.sqlserverexamples.com
>>sql

Infamous product level insufficient error message

This thing is driving me crazy. I have a simple flat .txt file I'm trying to import into a DB, and this USED to work perfectly with SQL Server 2000. With 2005, I get "product level insufficient."

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=217596

I've read that and I've looked around. It seems like the solution is to actually connect to the Windows box that the server itself is running on (where SSIS is installed) and import there?? But that's a pain.. that means I'd have to Remote Desktop into the server EVERY time I want to import a text file. Surely there's some other way to do this??

Any advice would be great. Thanks!I don't recognise the error message but the error itself sounds very familiar. Is this a double hop problem?|||Not sure what double hop is.

In SQL Server Management Studio, I'm trying to import a flat .txt file into the DB. Here's a screenshot of the error message (I highlighted it):

http://img59.imageshack.us/img59/319/prodinsuffrw4.gif|||Just looked on web. Looks different so I won't be much help. You seen this?
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=112469&SiteID=1|||Ahh, installing SP1 fixed it. Now I have a new problem but I'll research it a bit before posting :)sql

Indexing to prevent timeout expired message

sorry for posting a question that has probably been posted hundreds of
times, but i can't seem to find the answer i need...We're using a Sql
Server 7.0 database and recently started getting timeout expired
errors on our views, which i'm assuming is due to the volume of
records in our tables. Unfortunately i'm not too experiences w/
indexing tables, so my question is:
1) how do you determine which fields to index (does it have to be a
field w/ no nulls, no duplicates..similar to primary key), and why not
index the primary key
2) is it better to index the same field on different tables, or is it
a better design to index a different field for each table (ex. do you
want to index the same field that you link the different tables with,
or do you want to avoid doing this)
3) can somebody explain the concept of creating a clustered index
4) once table is indexed, if there are users accessing the linked
tables via Access, do they have to re-link the tables?

sorry for the number of questions and what may appear to be simple
questions to most, but again, i'm pretty unfamiliar w/ indexing and
would really appreciate any help...thanks"Danny" <dannytk@.mindspring.com> wrote in message
news:35a1d33f.0311031549.239ede2a@.posting.google.c om...
> sorry for posting a question that has probably been posted hundreds of
> times, but i can't seem to find the answer i need...We're using a Sql
> Server 7.0 database and recently started getting timeout expired
> errors on our views, which i'm assuming is due to the volume of
> records in our tables. Unfortunately i'm not too experiences w/
> indexing tables, so my question is:
> 1) how do you determine which fields to index (does it have to be a
> field w/ no nulls, no duplicates..similar to primary key), and why not
> index the primary key
> 2) is it better to index the same field on different tables, or is it
> a better design to index a different field for each table (ex. do you
> want to index the same field that you link the different tables with,
> or do you want to avoid doing this)
> 3) can somebody explain the concept of creating a clustered index
> 4) once table is indexed, if there are users accessing the linked
> tables via Access, do they have to re-link the tables?
> sorry for the number of questions and what may appear to be simple
> questions to most, but again, i'm pretty unfamiliar w/ indexing and
> would really appreciate any help...thanks

Indexing is big topic, and critical for performance, so I suggest you start
looking into the Books Online documentation on indexes and performance
tuning. You can find a lot of information on the web, too. One quick way to
get going would be to use the Index Tuning Wizard to recommend where you
should place indexes.

As for your questions above, here are some brief answers (which contain
plenty of over-simplification and over-generalization):

1. Look at the columns in the WHERE clauses of your queries. You can index
any column (except bit or computed columns in SQL7), or a combination of
columns. Adding more indexes to a table generally makes SELECTs faster, but
INSERT/UPDATEs slower.

2. Index the appropriate columns on each table - columns used in joins are
almost always worth indexing.

3. In a clustered index, the table data is sorted in the order of the index
(the index in fact holds the data), so you can only have one per table (and
most tables should have one). As a general rule, queries returning single
rows don't benefit much from a clustered index; queries returning a range of
rows, or an aggregate of a number of rows will benefit. Note that primary
keys are clustered by default, but this may not be the best choice.

4. Indexing is completely invisible to clients - they have no idea what
indexes, if any, are on the table. The exception would be if you create a
UNIQUE index, and the client performs an INSERT or UPDATE which would
violate the uniqueness. In that case, the client will get an error.

Simon