queries take a long time after sp2 installation

Has anyone had thsi issue, if so what was the fix?

We installed service pack2, the day after 2 of our production jobs started taking a long time to complete and causing a ton of blocking.

it went from running in 2 minutes to now taking 3 hours and 29 minutes to run. Can someone help?

Is it only certain queries running slower or is it all queries running slower? What high-level symptoms are you seeing? Does it look like CPU pressure, memory pressure, I/O pressure, blocking, etc.?

What kind of results do you get when you run these DMV queries?

-- Total waits are wait_time_ms (high signal waits indicates CPU pressure)

SELECT signal_wait_time_ms=SUM(signal_wait_time_ms)

,'%signal (cpu) waits' = CAST(100.0 * SUM(signal_wait_time_ms) / SUM (wait_time_ms) AS NUMERIC(20,2))

,resource_wait_time_ms=SUM(wait_time_ms - signal_wait_time_ms)

,'%resource waits'= CAST(100.0 * SUM(wait_time_ms - signal_wait_time_ms) / SUM (wait_time_ms) AS NUMERIC(20,2))

FROM sys.dm_os_wait_stats

-- Check SQL Server Schedulers to see if they are waiting on CPU

SELECT scheduler_id, current_tasks_count, runnable_tasks_count

FROM sys.dm_os_schedulers

WHERE scheduler_id < 255

-- Isolate top waits

WITH Waits AS

(

SELECT

wait_type,

wait_time_ms / 1000. AS wait_time_s,

100. * wait_time_ms / SUM(wait_time_ms) OVER() AS pct,

ROW_NUMBER() OVER(ORDER BY wait_time_ms DESC) AS rn

FROM sys.dm_os_wait_stats

WHERE wait_type NOT LIKE '%SLEEP%'

-- filter out additional irrelevant waits

)

SELECT

W1.wait_type,

CAST(W1.wait_time_s AS DECIMAL(12, 2)) AS wait_time_s,

CAST(W1.pct AS DECIMAL(12, 2)) AS pct,

CAST(SUM(W2.pct) AS DECIMAL(12, 2)) AS running_pct

FROM Waits AS W1

INNER JOIN Waits AS W2

ON W2.rn <= W1.rn

GROUP BY W1.rn, W1.wait_type, W1.wait_time_s, W1.pct

HAVING SUM(W2.pct) - W1.pct < 90 -- percentage threshold

ORDER BY W1.rn;

-- Detect blocking

SELECT blocked_query.session_id AS blocked_session_id,

blocking_query.session_id AS blocking_session_id,

sql_text.text AS blocked_text,

sql_btext.text AS blocking_text,

waits.wait_type AS blocking_resource

FROM sys.dm_exec_requests AS blocked_query

INNER JOIN sys.dm_exec_requests AS blocking_query

ON blocked_query.blocking_session_id = blocking_query.session_id

CROSS APPLY

(SELECT *

FROM sys.dm_exec_sql_text(blocking_query.sql_handle)

) sql_btext

CROSS APPLY

(SELECT *

FROM sys.dm_exec_sql_text(blocked_query.sql_handle)

) sql_text

INNER JOIN sys.dm_os_waiting_tasks AS waits

ON waits.session_id = blocking_query.session_id

|||After the SP2 Upgrade did you update the stats and index rebuilds on the tables?. You might want to perform some optimization and see if the problem still persists.|||

If you have not done so already, try running sp_UpdateStats on your database(s). This will run UPDATE STATISTICS with the default 10% sample rate on every table in the database (which may take a while, depending on your hardware and db size).

You should always do that after upgrading to SQL Server 2005

Rebuilding (as opposed to reorganizing) indexes will also automatically update statistics.

|||Hi,

We have experienced many slowness and trouble since the SP2 was installed.
Have a look at theses 2 KB:
http://support.microsoft.com/default.aspx/kb/937745
And
http://support.microsoft.com/default.aspx/kb/933564/en-us

Last point, run the following query when your server is slow:

select type, sum(single_pages_kb+multi_pages_kb) 'total memory' from sys.dm_os_memory_clerks ORDER by 2 DESC

This will help you to know what cache type is getting most of your SQL Ram.
If it's USERSTORE_TOKENPERM, consider using Trace flag 4618. It has had good impact on our system, but still not correct the case. I have conf call with MS Support on Monday about that point and will answer in this post if I have anymore informations.

Regards,
Jeremy
|||

Jeremy - Just wondering if you had any updates. We are currently hitting this issue. The clearing of ('TokenAndPermUserStore') does not work 100% of the time. We've experienced times when the system is so busy that we can not clear it fast enough.

We are considering using the trace flag.

Thanks -

Sam.

queries take a long time after sp2 installation

Has anyone had thsi issue, if so what was the fix?

We installed service pack2, the day after 2 of our production jobs started taking a long time to complete and causing a ton of blocking.

it went from running in 2 minutes to now taking 3 hours and 29 minutes to run. Can someone help?

Is it only certain queries running slower or is it all queries running slower? What high-level symptoms are you seeing? Does it look like CPU pressure, memory pressure, I/O pressure, blocking, etc.?

What kind of results do you get when you run these DMV queries?

-- Total waits are wait_time_ms (high signal waits indicates CPU pressure)

SELECT signal_wait_time_ms=SUM(signal_wait_time_ms)

,'%signal (cpu) waits'=CAST(100.0 *SUM(signal_wait_time_ms)/SUM(wait_time_ms)ASNUMERIC(20,2))

,resource_wait_time_ms=SUM(wait_time_ms - signal_wait_time_ms)

,'%resource waits'=CAST(100.0 *SUM(wait_time_ms - signal_wait_time_ms)/SUM(wait_time_ms)ASNUMERIC(20,2))

FROMsys.dm_os_wait_stats

-- Check SQL Server Schedulers to see if they are waiting on CPU

SELECT scheduler_id, current_tasks_count, runnable_tasks_count

FROMsys.dm_os_schedulers

WHERE scheduler_id < 255

-- Isolate top waits

WITH Waits AS

(

SELECT

wait_type,

wait_time_ms / 1000. AS wait_time_s,

100. * wait_time_ms /SUM(wait_time_ms)OVER()AS pct,

ROW_NUMBER()OVER(ORDERBY wait_time_ms DESC)AS rn

FROMsys.dm_os_wait_stats

WHERE wait_type NOTLIKE'%SLEEP%'

-- filter out additional irrelevant waits

)

SELECT

W1.wait_type,

CAST(W1.wait_time_s ASDECIMAL(12, 2))AS wait_time_s,

CAST(W1.pct ASDECIMAL(12, 2))AS pct,

CAST(SUM(W2.pct)ASDECIMAL(12, 2))AS running_pct

FROM Waits AS W1

INNERJOIN Waits AS W2

ON W2.rn <= W1.rn

GROUPBY W1.rn, W1.wait_type, W1.wait_time_s, W1.pct

HAVINGSUM(W2.pct)- W1.pct < 90 -- percentage threshold

ORDERBY W1.rn;

-- Detect blocking

SELECT blocked_query.session_id AS blocked_session_id,

blocking_query.session_id AS blocking_session_id,

sql_text.text AS blocked_text,

sql_btext.text AS blocking_text,

waits.wait_type AS blocking_resource

FROMsys.dm_exec_requestsAS blocked_query

INNERJOINsys.dm_exec_requestsAS blocking_query

ON blocked_query.blocking_session_id = blocking_query.session_id

CROSSAPPLY

(SELECT*

FROM sys.dm_exec_sql_text(blocking_query.sql_handle)

) sql_btext

CROSSAPPLY

(SELECT*

FROM sys.dm_exec_sql_text(blocked_query.sql_handle)

) sql_text

INNERJOINsys.dm_os_waiting_tasksAS waits

ON waits.session_id = blocking_query.session_id

|||After the SP2 Upgrade did you update the stats and index rebuilds on the tables?. You might want to perform some optimization and see if the problem still persists.|||

If you have not done so already, try running sp_UpdateStats on your database(s). This will run UPDATE STATISTICS with the default 10% sample rate on every table in the database (which may take a while, depending on your hardware and db size).

You should always do that after upgrading to SQL Server 2005

Rebuilding (as opposed to reorganizing) indexes will also automatically update statistics.

|||Hi,

We have experienced many slowness and trouble since the SP2 was installed.
Have a look at theses 2 KB:
http://support.microsoft.com/default.aspx/kb/937745
And
http://support.microsoft.com/default.aspx/kb/933564/en-us

Last point, run the following query when your server is slow:

select type, sum(single_pages_kb+multi_pages_kb) 'total memory' from sys.dm_os_memory_clerks ORDER by 2 DESC

This will help you to know what cache type is getting most of your SQL Ram.
If it's USERSTORE_TOKENPERM, consider using Trace flag 4618. It has had good impact on our system, but still not correct the case. I have conf call with MS Support on Monday about that point and will answer in this post if I have anymore informations.

Regards,
Jeremy
|||

Jeremy - Just wondering if you had any updates. We are currently hitting this issue. The clearing of ('TokenAndPermUserStore') does not work 100% of the time. We've experienced times when the system is so busy that we can not clear it fast enough.

We are considering using the trace flag.

Thanks -

Sam.

queries take a long time after sp2 installation

Has anyone had thsi issue, if so what was the fix?

We installed service pack2, the day after 2 of our production jobs started taking a long time to complete and causing a ton of blocking.

it went from running in 2 minutes to now taking 3 hours and 29 minutes to run. Can someone help?

Is it only certain queries running slower or is it all queries running slower? What high-level symptoms are you seeing? Does it look like CPU pressure, memory pressure, I/O pressure, blocking, etc.?

What kind of results do you get when you run these DMV queries?

-- Total waits are wait_time_ms (high signal waits indicates CPU pressure)

SELECT signal_wait_time_ms=SUM(signal_wait_time_ms)

,'%signal (cpu) waits'=CAST(100.0 *SUM(signal_wait_time_ms)/SUM(wait_time_ms)ASNUMERIC(20,2))

,resource_wait_time_ms=SUM(wait_time_ms - signal_wait_time_ms)

,'%resource waits'=CAST(100.0 *SUM(wait_time_ms - signal_wait_time_ms)/SUM(wait_time_ms)ASNUMERIC(20,2))

FROMsys.dm_os_wait_stats

-- Check SQL Server Schedulers to see if they are waiting on CPU

SELECT scheduler_id, current_tasks_count, runnable_tasks_count

FROMsys.dm_os_schedulers

WHERE scheduler_id < 255

-- Isolate top waits

WITH Waits AS

(

SELECT

wait_type,

wait_time_ms / 1000. AS wait_time_s,

100. * wait_time_ms /SUM(wait_time_ms)OVER()AS pct,

ROW_NUMBER()OVER(ORDERBY wait_time_ms DESC)AS rn

FROMsys.dm_os_wait_stats

WHERE wait_type NOTLIKE'%SLEEP%'

-- filter out additional irrelevant waits

)

SELECT

W1.wait_type,

CAST(W1.wait_time_s ASDECIMAL(12, 2))AS wait_time_s,

CAST(W1.pct ASDECIMAL(12, 2))AS pct,

CAST(SUM(W2.pct)ASDECIMAL(12, 2))AS running_pct

FROM Waits AS W1

INNERJOIN Waits AS W2

ON W2.rn <= W1.rn

GROUPBY W1.rn, W1.wait_type, W1.wait_time_s, W1.pct

HAVINGSUM(W2.pct)- W1.pct < 90 -- percentage threshold

ORDERBY W1.rn;

-- Detect blocking

SELECT blocked_query.session_id AS blocked_session_id,

blocking_query.session_id AS blocking_session_id,

sql_text.text AS blocked_text,

sql_btext.text AS blocking_text,

waits.wait_type AS blocking_resource

FROMsys.dm_exec_requestsAS blocked_query

INNERJOINsys.dm_exec_requestsAS blocking_query

ON blocked_query.blocking_session_id = blocking_query.session_id

CROSSAPPLY

(SELECT*

FROM sys.dm_exec_sql_text(blocking_query.sql_handle)

) sql_btext

CROSSAPPLY

(SELECT*

FROM sys.dm_exec_sql_text(blocked_query.sql_handle)

) sql_text

INNERJOINsys.dm_os_waiting_tasksAS waits

ON waits.session_id = blocking_query.session_id

|||After the SP2 Upgrade did you update the stats and index rebuilds on the tables?. You might want to perform some optimization and see if the problem still persists.|||

If you have not done so already, try running sp_UpdateStats on your database(s). This will run UPDATE STATISTICS with the default 10% sample rate on every table in the database (which may take a while, depending on your hardware and db size).

You should always do that after upgrading to SQL Server 2005

Rebuilding (as opposed to reorganizing) indexes will also automatically update statistics.

|||Hi,

We have experienced many slowness and trouble since the SP2 was installed.
Have a look at theses 2 KB:
http://support.microsoft.com/default.aspx/kb/937745
And
http://support.microsoft.com/default.aspx/kb/933564/en-us

Last point, run the following query when your server is slow:

select type, sum(single_pages_kb+multi_pages_kb) 'total memory' from sys.dm_os_memory_clerks ORDER by 2 DESC

This will help you to know what cache type is getting most of your SQL Ram.
If it's USERSTORE_TOKENPERM, consider using Trace flag 4618. It has had good impact on our system, but still not correct the case. I have conf call with MS Support on Monday about that point and will answer in this post if I have anymore informations.

Regards,
Jeremy
|||

Jeremy - Just wondering if you had any updates. We are currently hitting this issue. The clearing of ('TokenAndPermUserStore') does not work 100% of the time. We've experienced times when the system is so busy that we can not clear it fast enough.

We are considering using the trace flag.

Thanks -

Sam.

quality of service

I have been having what I believe to be quality of service issues with the c
ompany that hosts my company's web site and connected SQL Server database.
The same stored procedure is called from a number of different web pages wit
h identical parameter specs
, etc. (they were all created from the same template web page). Over the pa
st three weeks, this stored procedure has been called more than 20,000 times
by more than 1,000 different end users, and has failed to drop a table it c
reates 70 of these times (a
99.7% successful execution rate), which causes significant problems for the
end user, since the next time this procedure is called, the table already ex
ists. There is seemingly no pattern to these failed executions with regard
to particular end users, o
r to which pages from which they were called. However, there is a pattern i
n the timing. All but 4 of the failed executions occurred clustered around
about 10 very specific time stamps (i.e., 5 of the tables that were not drop
ped were created within a m
inute of 2:27 pm, 15 of the tables that were not dropped were created within
1 minute of 2:27 pm, etc.). The company that hosts my web site and connect
ed SQL Server database insists that the problem is in my scripting and refus
e to look into the issue un
less I pay them $120 per hour to do so. It seems to me that, if this were s
cripting error, it probably would not be succeeding 99.7% of the time, and a
ny failures that did occur would be randomly distributed, not clustered arou
nd specific time stamps. I
t seems to me that this clustering is indicative of slowed or failed SQL Ser
ver responses due to server performance issues. I work in statistics and ha
ve calculated the odds of this time clustering being random, and, even with
the most conservative estim
ates, it works out to be on in a number I don't even know the name for (with
more than 40 zeros). I have included a little information about the stored
procedure below, if you think it is relevant. my question to you is: Does t
his seem likely to be a scr
ipting issue or a server performance issue?
Part of the stored procedure uses the sp_executesql command with a text stri
ng to create a table with the unique name of the end user ID (a unique, rand
omly generated 12 character alphanumeric ID), inserts data into this new tab
le through a loop, then pul
ls a record set from the table, and drops the table (there is a good reason
I need to generate the recordset this way).
Thank you for your help!
SQL SearcherWhy can't you use a temp table? That's what they're there for...
"SQL Searcher" <anonymous@.discussions.microsoft.com> wrote in message
news:FB3A473E-7ED7-4E01-A8F9-95F7ABA12313@.microsoft.com...
> I have been having what I believe to be quality of service issues with the
company that hosts my company's web site and connected SQL Server database.
The same stored procedure is called from a number of different web pages
with identical parameter specs, etc. (they were all created from the same
template web page). Over the past three weeks, this stored procedure has
been called more than 20,000 times by more than 1,000 different end users,
and has failed to drop a table it creates 70 of these times (a 99.7%
successful execution rate), which causes significant problems for the end
user, since the next time this procedure is called, the table already
exists. There is seemingly no pattern to these failed executions with
regard to particular end users, or to which pages from which they were
called. However, there is a pattern in the timing. All but 4 of the failed
executions occurred clustered around about 10 very specific time stamps
(i.e., 5 of the tables that were not dropped were created within a minute of
2:27 pm, 15 of the tables that were not dropped were created within 1 minute
of 2:27 pm, etc.). The company that hosts my web site and connected SQL
Server database insists that the problem is in my scripting and refuse to
look into the issue unless I pay them $120 per hour to do so. It seems to
me that, if this were scripting error, it probably would not be succeeding
99.7% of the time, and any failures that did occur would be randomly
distributed, not clustered around specific time stamps. It seems to me that
this clustering is indicative of slowed or failed SQL Server responses due
to server performance issues. I work in statistics and have calculated the
odds of this time clustering being random, and, even with the most
conservative estimates, it works out to be on in a number I don't even know
the name for (with more than 40 zeros). I have included a little information
about the stored procedure below, if you think it is relevant. my question
to you is: Does this seem likely to be a scripting issue or a server
performance issue?
> Part of the stored procedure uses the sp_executesql command with a text
string to create a table with the unique name of the end user ID (a unique,
randomly generated 12 character alphanumeric ID), inserts data into this new
table through a loop, then pulls a record set from the table, and drops the
table (there is a good reason I need to generate the recordset this way).
> Thank you for your help!
> SQL Searcher|||I tried, and it didn't work for some reason.

quality of service

I have been having what I believe to be quality of service issues with the company that hosts my company's web site and connected SQL Server database. The same stored procedure is called from a number of different web pages with identical parameter specs, etc. (they were all created from the same template web page). Over the past three weeks, this stored procedure has been called more than 20,000 times by more than 1,000 different end users, and has failed to drop a table it creates 70 of these times (a 99.7% successful execution rate), which causes significant problems for the end user, since the next time this procedure is called, the table already exists. There is seemingly no pattern to these failed executions with regard to particular end users, or to which pages from which they were called. However, there is a pattern in the timing. All but 4 of the failed executions occurred clustered around about 10 very specific time stamps (i.e., 5 of the tables that were not dropped were created within a minute of 2:27 pm, 15 of the tables that were not dropped were created within 1 minute of 2:27 pm, etc.). The company that hosts my web site and connected SQL Server database insists that the problem is in my scripting and refuse to look into the issue unless I pay them $120 per hour to do so. It seems to me that, if this were scripting error, it probably would not be succeeding 99.7% of the time, and any failures that did occur would be randomly distributed, not clustered around specific time stamps. It seems to me that this clustering is indicative of slowed or failed SQL Server responses due to server performance issues. I work in statistics and have calculated the odds of this time clustering being random, and, even with the most conservative estimates, it works out to be on in a number I don't even know the name for (with more than 40 zeros). I have included a little information about the stored procedure below, if you think it is relevant. my question to you is: Does this seem likely to be a scripting issue or a server performance issue?
Part of the stored procedure uses the sp_executesql command with a text string to create a table with the unique name of the end user ID (a unique, randomly generated 12 character alphanumeric ID), inserts data into this new table through a loop, then pulls a record set from the table, and drops the table (there is a good reason I need to generate the recordset this way).
Thank you for your help
SQL SearcherWhy can't you use a temp table? That's what they're there for...
"SQL Searcher" <anonymous@.discussions.microsoft.com> wrote in message
news:FB3A473E-7ED7-4E01-A8F9-95F7ABA12313@.microsoft.com...
> I have been having what I believe to be quality of service issues with the
company that hosts my company's web site and connected SQL Server database.
The same stored procedure is called from a number of different web pages
with identical parameter specs, etc. (they were all created from the same
template web page). Over the past three weeks, this stored procedure has
been called more than 20,000 times by more than 1,000 different end users,
and has failed to drop a table it creates 70 of these times (a 99.7%
successful execution rate), which causes significant problems for the end
user, since the next time this procedure is called, the table already
exists. There is seemingly no pattern to these failed executions with
regard to particular end users, or to which pages from which they were
called. However, there is a pattern in the timing. All but 4 of the failed
executions occurred clustered around about 10 very specific time stamps
(i.e., 5 of the tables that were not dropped were created within a minute of
2:27 pm, 15 of the tables that were not dropped were created within 1 minute
of 2:27 pm, etc.). The company that hosts my web site and connected SQL
Server database insists that the problem is in my scripting and refuse to
look into the issue unless I pay them $120 per hour to do so. It seems to
me that, if this were scripting error, it probably would not be succeeding
99.7% of the time, and any failures that did occur would be randomly
distributed, not clustered around specific time stamps. It seems to me that
this clustering is indicative of slowed or failed SQL Server responses due
to server performance issues. I work in statistics and have calculated the
odds of this time clustering being random, and, even with the most
conservative estimates, it works out to be on in a number I don't even know
the name for (with more than 40 zeros). I have included a little information
about the stored procedure below, if you think it is relevant. my question
to you is: Does this seem likely to be a scripting issue or a server
performance issue?
> Part of the stored procedure uses the sp_executesql command with a text
string to create a table with the unique name of the end user ID (a unique,
randomly generated 12 character alphanumeric ID), inserts data into this new
table through a loop, then pulls a record set from the table, and drops the
table (there is a good reason I need to generate the recordset this way).
> Thank you for your help!
> SQL Searcher|||I tried, and it didn't work for some reason.

QN Best Practices

Hi everyone,

I wonder if somebody here could recommend a good article about MS Service Broker. I'm looking for some advice and tips in designing applications using SQL Service Broker, mainly QN. For instance, maintenance routines and common faulty scenarios I might find later when my solution is implemented. I have googled for a while but all I can find are recopied examples of QN.

Thanks

Are you interested in SSB best practices in general or specifically QN practices? The (typical) QN use of SSB is very limited (local only, a very limited message exchange pattern, conversations are created by the system for you etc etc). What are your main concerns?

QFE 859

We are attempting to install SQL Reporting Services using a network service
account for the ReportServer service. This configuration will fail without
installing QFE 859. There is allegedly a hotfix installer which will apply
the necessary hotfix, but the Microsoft KB articles go in circles without
ever offering a download.
Does anyone know where to download this hotfix and/or why Microsoft has
chosen to hide it so carefully?
The links I'm directed to are: http://support.microsoft.com/?id=821334 and
http://support.microsoft.com/kb/330391/I noticed this myself awhile back. I think what has happened is that they
pulled it because SP4 was out. SP4 is cumulative so it should work for you
(of course SP4 has a problem that requires a hotfix if you have more than 2
Gig of RAM and AWE enabled).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lowell Williams" <Lowell Williams@.discussions.microsoft.com> wrote in
message news:2DC69A07-1D0F-48D6-BE42-773B8029219B@.microsoft.com...
> We are attempting to install SQL Reporting Services using a network
> service
> account for the ReportServer service. This configuration will fail
> without
> installing QFE 859. There is allegedly a hotfix installer which will
> apply
> the necessary hotfix, but the Microsoft KB articles go in circles without
> ever offering a download.
> Does anyone know where to download this hotfix and/or why Microsoft has
> chosen to hide it so carefully?
> The links I'm directed to are: http://support.microsoft.com/?id=821334
> and
> http://support.microsoft.com/kb/330391/|||Thanks for the reply, Bruce.
Unfortunately, we're not ready to go down the SP4 road yet. It boggles the
mind that a hotfix would be pulled when there are so many different
configurations out there.
I suppose we'll have to use a domain account if the original hotfix file
really is unavailable.
Any other suggestions are appreciated.
"Bruce L-C [MVP]" wrote:
> I noticed this myself awhile back. I think what has happened is that they
> pulled it because SP4 was out. SP4 is cumulative so it should work for you
> (of course SP4 has a problem that requires a hotfix if you have more than 2
> Gig of RAM and AWE enabled).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Lowell Williams" <Lowell Williams@.discussions.microsoft.com> wrote in
> message news:2DC69A07-1D0F-48D6-BE42-773B8029219B@.microsoft.com...
> > We are attempting to install SQL Reporting Services using a network
> > service
> > account for the ReportServer service. This configuration will fail
> > without
> > installing QFE 859. There is allegedly a hotfix installer which will
> > apply
> > the necessary hotfix, but the Microsoft KB articles go in circles without
> > ever offering a download.
> >
> > Does anyone know where to download this hotfix and/or why Microsoft has
> > chosen to hide it so carefully?
> >
> > The links I'm directed to are: http://support.microsoft.com/?id=821334
> > and
> > http://support.microsoft.com/kb/330391/
>
>|||You could also call support. It should be a free call.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lowell Williams" <LowellWilliams@.discussions.microsoft.com> wrote in
message news:33ECDA63-BCB5-4469-9E81-9EEBAAB6E22C@.microsoft.com...
> Thanks for the reply, Bruce.
> Unfortunately, we're not ready to go down the SP4 road yet. It boggles
> the
> mind that a hotfix would be pulled when there are so many different
> configurations out there.
> I suppose we'll have to use a domain account if the original hotfix file
> really is unavailable.
> Any other suggestions are appreciated.
> "Bruce L-C [MVP]" wrote:
>> I noticed this myself awhile back. I think what has happened is that they
>> pulled it because SP4 was out. SP4 is cumulative so it should work for
>> you
>> (of course SP4 has a problem that requires a hotfix if you have more than
>> 2
>> Gig of RAM and AWE enabled).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Lowell Williams" <Lowell Williams@.discussions.microsoft.com> wrote in
>> message news:2DC69A07-1D0F-48D6-BE42-773B8029219B@.microsoft.com...
>> > We are attempting to install SQL Reporting Services using a network
>> > service
>> > account for the ReportServer service. This configuration will fail
>> > without
>> > installing QFE 859. There is allegedly a hotfix installer which will
>> > apply
>> > the necessary hotfix, but the Microsoft KB articles go in circles
>> > without
>> > ever offering a download.
>> >
>> > Does anyone know where to download this hotfix and/or why Microsoft has
>> > chosen to hide it so carefully?
>> >
>> > The links I'm directed to are: http://support.microsoft.com/?id=821334
>> > and
>> > http://support.microsoft.com/kb/330391/
>>|||Did you get it resolved? Did you have to call? We have the identical
problem here.
"Lowell Williams" wrote:
> We are attempting to install SQL Reporting Services using a network service
> account for the ReportServer service. This configuration will fail without
> installing QFE 859. There is allegedly a hotfix installer which will apply
> the necessary hotfix, but the Microsoft KB articles go in circles without
> ever offering a download.
> Does anyone know where to download this hotfix and/or why Microsoft has
> chosen to hide it so carefully?
> The links I'm directed to are: http://support.microsoft.com/?id=821334 and
> http://support.microsoft.com/kb/330391/|||My guess is that this is part of Windows 2003 SP1. If you install SP1 you
should not need the hotfix. If you do not want to install SP1 then I would
think you need to contact support to get the hotfix.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:95CA7B1D-AAC1-45E4-9E8C-6687586B1BDC@.microsoft.com...
> Did you get it resolved? Did you have to call? We have the identical
> problem here.
>
> "Lowell Williams" wrote:
>> We are attempting to install SQL Reporting Services using a network
>> service
>> account for the ReportServer service. This configuration will fail
>> without
>> installing QFE 859. There is allegedly a hotfix installer which will
>> apply
>> the necessary hotfix, but the Microsoft KB articles go in circles without
>> ever offering a download.
>> Does anyone know where to download this hotfix and/or why Microsoft has
>> chosen to hide it so carefully?
>> The links I'm directed to are: http://support.microsoft.com/?id=821334
>> and
>> http://support.microsoft.com/kb/330391/|||We got it resolved by installing the patch, but to get it we did an end run
by having a Microsoft Partner call in to get it. I believe it took him about
five phone calls.
We started with the 800 number for partner support and went from there.
Make sure you have details available when you call in. I assume the regular
support number should get you there, and since a hotfix will solve your
problem, there should be no charge for the call (I think). Have KB article#
references from my original post, your SQL license and patch level, your
Server versions, etc. all at your fingertips when you call.
I've pasted part of the link they sent us for the patch below which might
help MS support figure out what you want. It has an expiring password on
it, so it won't help you to d/l it now... They also hinted that the patch
was customized to particular environments, and that they had to "configure"
it for us.
It was a little difficult to get them to realize what patch we wanted until
they finally transferred us to the SQL group.
"Bug470536/873/free/150452_ENU_i386_zip.exe"
Hope this helps, and good luck!
Lowell
"Rob" wrote:
> Did you get it resolved? Did you have to call? We have the identical
> problem here.
>
> "Lowell Williams" wrote:
> > We are attempting to install SQL Reporting Services using a network service
> > account for the ReportServer service. This configuration will fail without
> > installing QFE 859. There is allegedly a hotfix installer which will apply
> > the necessary hotfix, but the Microsoft KB articles go in circles without
> > ever offering a download.
> >
> > Does anyone know where to download this hotfix and/or why Microsoft has
> > chosen to hide it so carefully?
> >
> > The links I'm directed to are: http://support.microsoft.com/?id=821334 and
> > http://support.microsoft.com/kb/330391/|||I forgot to mention that there are two versions of this hotfix. You'll want
to verify with Microsoft which version you need.
The two files are called:
SQL2000-KB810185-8.00.0873-ENU.exe
SQL2000-KB884856-v8.00.0977-x86-ENU.exe
Those embedded KB articles should be of help when calling, too.
"Rob" wrote:
> Did you get it resolved? Did you have to call? We have the identical
> problem here.
>
> "Lowell Williams" wrote:
> > We are attempting to install SQL Reporting Services using a network service
> > account for the ReportServer service. This configuration will fail without
> > installing QFE 859. There is allegedly a hotfix installer which will apply
> > the necessary hotfix, but the Microsoft KB articles go in circles without
> > ever offering a download.
> >
> > Does anyone know where to download this hotfix and/or why Microsoft has
> > chosen to hide it so carefully?
> >
> > The links I'm directed to are: http://support.microsoft.com/?id=821334 and
> > http://support.microsoft.com/kb/330391/|||Thanks for all your help. I ended up installing SP4 and that also resolved
the issue.
"Lowell Williams" wrote:
> I forgot to mention that there are two versions of this hotfix. You'll want
> to verify with Microsoft which version you need.
>
> The two files are called:
> SQL2000-KB810185-8.00.0873-ENU.exe
> SQL2000-KB884856-v8.00.0977-x86-ENU.exe
> Those embedded KB articles should be of help when calling, too.
> "Rob" wrote:
> > Did you get it resolved? Did you have to call? We have the identical
> > problem here.
> >
> >
> > "Lowell Williams" wrote:
> >
> > > We are attempting to install SQL Reporting Services using a network service
> > > account for the ReportServer service. This configuration will fail without
> > > installing QFE 859. There is allegedly a hotfix installer which will apply
> > > the necessary hotfix, but the Microsoft KB articles go in circles without
> > > ever offering a download.
> > >
> > > Does anyone know where to download this hotfix and/or why Microsoft has
> > > chosen to hide it so carefully?
> > >
> > > The links I'm directed to are: http://support.microsoft.com/?id=821334 and
> > > http://support.microsoft.com/kb/330391/

q; using SSIS

Where do I start to use SSIS in SQL 2005? Service seems running but I do not
know how to start using it.
You can use the SQL Server Business Intelligence Development Studio to
develop SSIS packages. BI Studio is the Visual Studio IDE with specialized
SQL Server BI project types.
See the SQL Server Books Online
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/sqlovr9/html/44003d30-de23-4493-9631-2b53936a8564.htm)
for more information..
Hope this helps.
Dan Guzman
SQL Server MVP
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:96B427C0-034C-463B-8EA6-E60173E7777B@.microsoft.com...
> Where do I start to use SSIS in SQL 2005? Service seems running but I do
> not
> know how to start using it.

q; using SSIS

Where do I start to use SSIS in SQL 2005? Service seems running but I do not
know how to start using it.You can use the SQL Server Business Intelligence Development Studio to
develop SSIS packages. BI Studio is the Visual Studio IDE with specialized
SQL Server BI project types.
See the SQL Server Books Online
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/sqlovr9/html/44003d30-de23-4493-9631-2b53936a8564.htm)
for more information..
--
Hope this helps.
Dan Guzman
SQL Server MVP
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:96B427C0-034C-463B-8EA6-E60173E7777B@.microsoft.com...
> Where do I start to use SSIS in SQL 2005? Service seems running but I do
> not
> know how to start using it.

q; using SSIS

Where do I start to use SSIS in SQL 2005? Service seems running but I do not
know how to start using it.You can use the SQL Server Business Intelligence Development Studio to
develop SSIS packages. BI Studio is the Visual Studio IDE with specialized
SQL Server BI project types.
See the SQL Server Books Online
(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/sqlovr9/html/44003d30-de23-4493-9631-
2b53936a8564.htm)
for more information..
Hope this helps.
Dan Guzman
SQL Server MVP
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:96B427C0-034C-463B-8EA6-E60173E7777B@.microsoft.com...
> Where do I start to use SSIS in SQL 2005? Service seems running but I do
> not
> know how to start using it.

Q: SP2

Hello,
Is RS service packs cumulative, meaning can I just directly install SP2
without SP1?
Thanks,yes u can install the SP2 it includes the sp1
"JIM.H." wrote:
> Hello,
> Is RS service packs cumulative, meaning can I just directly install SP2
> without SP1?
> Thanks,
>

q: reporting service in SQL 2005

Hello,
I installed SQL Server 2005 into a Windows 2005 Pro machine, will I be able
to use Reporting service to deploy the reports here? Is there any web site
that show step by step how I can do that?
Thanks,On Sun, 21 May 2006 04:59:02 -0700, JIM.H.
<JIMH@.discussions.microsoft.com> wrote:

>Hello,
>I installed SQL Server 2005 into a Windows 2005 Pro machine, will I be able
>to use Reporting service to deploy the reports here? Is there any web site
>that show step by step how I can do that?
>Thanks,
Jim,
There is no Windows 2005. I guess you mean Windows XP Pro.
XP Pro is really appropriate only for a development machine for SQL
Server 2005.There are technical and potential licensing issues.
Questions on Reporting Services are better directed to the
microsoft.public.sqlserver.reportingsvcs newsgroup.
There is series of webcasts under way on Reporting Services 2005 at
http://www.microsoft.com/events.
Andrew Watt MVP

q: reporting service in SQL 2005

Hello,
I installed SQL Server 2005 into a Windows 2005 Pro machine, will I be able
to use Reporting service to deploy the reports here? Is there any web site
that show step by step how I can do that?
Thanks,On Sun, 21 May 2006 04:59:02 -0700, JIM.H.
<JIMH@.discussions.microsoft.com> wrote:
>Hello,
>I installed SQL Server 2005 into a Windows 2005 Pro machine, will I be able
>to use Reporting service to deploy the reports here? Is there any web site
>that show step by step how I can do that?
>Thanks,
Jim,
There is no Windows 2005. I guess you mean Windows XP Pro.
XP Pro is really appropriate only for a development machine for SQL
Server 2005.There are technical and potential licensing issues.
Questions on Reporting Services are better directed to the
microsoft.public.sqlserver.reportingsvcs newsgroup.
There is series of webcasts under way on Reporting Services 2005 at
http://www.microsoft.com/events.
Andrew Watt MVP

q: reporting service 2005

Hello,
I installed SQL Server 2005 into a Windows 2000 Pro machine, I have
following question:
1. will I be able to use Reporting services to deploy the reports to the
same machine as a report server?
2. Can I modify and deploy mo old reports written in RS2000
3. Is there any web site that show step by step how I can work with RS2005?
Thanks,On Sun, 21 May 2006 09:36:01 -0700, JIM.H.
<JIMH@.discussions.microsoft.com> wrote:
>Hello,
>I installed SQL Server 2005 into a Windows 2000 Pro machine, I have
>following question:
>1. will I be able to use Reporting services to deploy the reports to the
>same machine as a report server?
Yes, you should be able to do that. Consider performance implications
if the server is anything but lightly loaded.
>2. Can I modify and deploy mo old reports written in RS2000
Yes, but it's a one way process (for most practical purposes). Once
you have opened an RS2000 report in BIDS and deployed it on RS2005 you
won't be able (without some hand editing) to deploy the report at a
future date on an RS2000 server.
If you have a possible need to return/use RS2000 make a backup in the
old format before deploying on RS2005.
>3. Is there any web site that show step by step how I can work with RS2005?
Books Online has a lot of useful information.
Also take a look at http://www.microsoft.com/events. There is a series
of RS2005 webcasts underway.
Andrew Watt MVP
>Thanks,