long running jobs crashing the box

Ive a got an sql server that crashes whenever a job runs for a minimum of
5 - 10 minutes. It doesnt happen 100% of the time, probably 80-90%. It
doesnt matter if the job is scheduled, run manually, a backup, a reindex, a
data transfer, whatever, if it runs between 5 and 10 minutes, the box
crashes. Of course it happens most frquently during backups as they are run
the most. All ideas are appreicated.
--
SQL2K SP3
TIA, ChrisR"ChrisR" <bla@.noemail.com> wrote in message
news:u%23$pQDT4EHA.936@.TK2MSFTNGP12.phx.gbl...
> Ive a got an sql server that crashes whenever a job runs for a minimum of
> 5 - 10 minutes. It doesnt happen 100% of the time, probably 80-90%. It
> doesnt matter if the job is scheduled, run manually, a backup, a reindex,
> a
> data transfer, whatever, if it runs between 5 and 10 minutes, the box
> crashes. Of course it happens most frquently during backups as they are
> run
> the most. All ideas are appreicated.
> --
> SQL2K SP3
> TIA, ChrisR
>
What do you mean by crashes? Does the O/S die and you get a blue screen?
Does SQL Server stop running, but the O/S is okay?
What version of O/S, what version of SQL Server? What service packs have
you installed.
What are you using for backups? Is it a standard SQL Server backup or are
you using some other program?
More information would be helpful.
Rick Sawtell
MCT, MCSD, MCDBA|||> What do you mean by crashes? Does the O/S die and you get a blue screen?
> Does SQL Server stop running, but the O/S is okay?
Blue screen.
> What version of O/S, what version of SQL Server? What service packs have
> you installed.
Win2K sp4
SQL2K sp3a
> What are you using for backups? Is it a standard SQL Server backup or are
> you using some other program?
Standard SQL.
Let me know if more info is required.
Thanks, ChrisR
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:OZwiGUT4EHA.1452@.TK2MSFTNGP11.phx.gbl...
> "ChrisR" <bla@.noemail.com> wrote in message
> news:u%23$pQDT4EHA.936@.TK2MSFTNGP12.phx.gbl...
> > Ive a got an sql server that crashes whenever a job runs for a minimum
of
> > 5 - 10 minutes. It doesnt happen 100% of the time, probably 80-90%. It
> > doesnt matter if the job is scheduled, run manually, a backup, a
reindex,
> > a
> > data transfer, whatever, if it runs between 5 and 10 minutes, the box
> > crashes. Of course it happens most frquently during backups as they are
> > run
> > the most. All ideas are appreicated.
> >
> > --
> > SQL2K SP3
> >
> > TIA, ChrisR
> >
> >
> What do you mean by crashes? Does the O/S die and you get a blue screen?
> Does SQL Server stop running, but the O/S is okay?
> What version of O/S, what version of SQL Server? What service packs have
> you installed.
> What are you using for backups? Is it a standard SQL Server backup or are
> you using some other program?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||What does the Application Log say?
Do you have anything else running on that server besides SQL 2k? (Exchange
maybe?).
Have you tried setting a max server memory for SQL Server? Tune it down a
bit and ensure that you leave enough RAM for the O/S.
(EM-> right-click on Server, Properties)
Rick Sawtell
MCT, MCSD, MCDBA|||The Event Viewer just says "the shut down at (time) was unexpected."
I just changed the memory so we'll see if that fixes anything.
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:OPykeeU4EHA.4092@.TK2MSFTNGP14.phx.gbl...
> What does the Application Log say?
> Do you have anything else running on that server besides SQL 2k?
(Exchange
> maybe?).
> Have you tried setting a max server memory for SQL Server? Tune it down a
> bit and ensure that you leave enough RAM for the O/S.
> (EM-> right-click on Server, Properties)
> Rick Sawtell
> MCT, MCSD, MCDBA
>

long running jobs crashing the box

Ive a got an sql server that crashes whenever a job runs for a minimum of
5 - 10 minutes. It doesnt happen 100% of the time, probably 80-90%. It
doesnt matter if the job is scheduled, run manually, a backup, a reindex, a
data transfer, whatever, if it runs between 5 and 10 minutes, the box
crashes. Of course it happens most frquently during backups as they are run
the most. All ideas are appreicated.
SQL2K SP3
TIA, ChrisR
"ChrisR" <bla@.noemail.com> wrote in message
news:u%23$pQDT4EHA.936@.TK2MSFTNGP12.phx.gbl...
> Ive a got an sql server that crashes whenever a job runs for a minimum of
> 5 - 10 minutes. It doesnt happen 100% of the time, probably 80-90%. It
> doesnt matter if the job is scheduled, run manually, a backup, a reindex,
> a
> data transfer, whatever, if it runs between 5 and 10 minutes, the box
> crashes. Of course it happens most frquently during backups as they are
> run
> the most. All ideas are appreicated.
> --
> SQL2K SP3
> TIA, ChrisR
>
What do you mean by crashes? Does the O/S die and you get a blue screen?
Does SQL Server stop running, but the O/S is okay?
What version of O/S, what version of SQL Server? What service packs have
you installed.
What are you using for backups? Is it a standard SQL Server backup or are
you using some other program?
More information would be helpful.
Rick Sawtell
MCT, MCSD, MCDBA
|||> What do you mean by crashes? Does the O/S die and you get a blue screen?
> Does SQL Server stop running, but the O/S is okay?
Blue screen.

> What version of O/S, what version of SQL Server? What service packs have
> you installed.
Win2K sp4
SQL2K sp3a

> What are you using for backups? Is it a standard SQL Server backup or are
> you using some other program?
Standard SQL.
Let me know if more info is required.
Thanks, ChrisR
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:OZwiGUT4EHA.1452@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> "ChrisR" <bla@.noemail.com> wrote in message
> news:u%23$pQDT4EHA.936@.TK2MSFTNGP12.phx.gbl...
of[vbcol=seagreen]
reindex,
> What do you mean by crashes? Does the O/S die and you get a blue screen?
> Does SQL Server stop running, but the O/S is okay?
> What version of O/S, what version of SQL Server? What service packs have
> you installed.
> What are you using for backups? Is it a standard SQL Server backup or are
> you using some other program?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||What does the Application Log say?
Do you have anything else running on that server besides SQL 2k? (Exchange
maybe?).
Have you tried setting a max server memory for SQL Server? Tune it down a
bit and ensure that you leave enough RAM for the O/S.
(EM-> right-click on Server, Properties)
Rick Sawtell
MCT, MCSD, MCDBA
|||The Event Viewer just says "the shut down at (time) was unexpected."
I just changed the memory so we'll see if that fixes anything.
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:OPykeeU4EHA.4092@.TK2MSFTNGP14.phx.gbl...
> What does the Application Log say?
> Do you have anything else running on that server besides SQL 2k?
(Exchange
> maybe?).
> Have you tried setting a max server memory for SQL Server? Tune it down a
> bit and ensure that you leave enough RAM for the O/S.
> (EM-> right-click on Server, Properties)
> Rick Sawtell
> MCT, MCSD, MCDBA
>
sql

Long Queries Hang VS; Other Productivity Killers

Whenever I run long SQL in VS whether it's in the Data tab or in Preview
mode, I can't seem to get a report out of it. I'm talking SQL in excess of
200 lines.
I can run the SQL fine in Query Analyzer but running it in the Data tab, it
freezes VS, and when I run the Preview, the report never renders. I have even
tried hardcoding all parameters, creating a stored procedure, and running the
report off a view. None have resolved the issue.
On a possibly related note, my connection to the database times out
intermittently, saying:
--
Microsoft Development Environment
--
An error occurred while executing the query.
General network error. Check your network documentation.
--
OK
--
This absolutely kills me over the course of a day. I have to shut down VS
and restart it.
Is my Reporting Services VS package install corrupt? What do I do?How many fields are being returned? How many rows of data?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> Whenever I run long SQL in VS whether it's in the Data tab or in Preview
> mode, I can't seem to get a report out of it. I'm talking SQL in excess of
> 200 lines.
> I can run the SQL fine in Query Analyzer but running it in the Data tab,
it
> freezes VS, and when I run the Preview, the report never renders. I have
even
> tried hardcoding all parameters, creating a stored procedure, and running
the
> report off a view. None have resolved the issue.
> On a possibly related note, my connection to the database times out
> intermittently, saying:
> --
> Microsoft Development Environment
> --
> An error occurred while executing the query.
> General network error. Check your network documentation.
> --
> OK
> --
> This absolutely kills me over the course of a day. I have to shut down VS
> and restart it.
> Is my Reporting Services VS package install corrupt? What do I do?|||For one report in particular, about 727 rows, and today it's taking just over
4 minutes to run. The other has over 60,000 rows and I'm just going to have
to work on limiting that severely.
"Bruce L-C [MVP]" wrote:
> How many fields are being returned? How many rows of data?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > Whenever I run long SQL in VS whether it's in the Data tab or in Preview
> > mode, I can't seem to get a report out of it. I'm talking SQL in excess of
> > 200 lines.
> >
> > I can run the SQL fine in Query Analyzer but running it in the Data tab,
> it
> > freezes VS, and when I run the Preview, the report never renders. I have
> even
> > tried hardcoding all parameters, creating a stored procedure, and running
> the
> > report off a view. None have resolved the issue.
> >
> > On a possibly related note, my connection to the database times out
> > intermittently, saying:
> >
> > --
> > Microsoft Development Environment
> > --
> > An error occurred while executing the query.
> >
> > General network error. Check your network documentation.
> > --
> > OK
> > --
> >
> > This absolutely kills me over the course of a day. I have to shut down VS
> > and restart it.
> >
> > Is my Reporting Services VS package install corrupt? What do I do?
>
>|||The 727 rows should not be a problem. Is that one causing an issue from the
data tab?
It doesn't surprise me that the 60,000 row one has problems.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> For one report in particular, about 727 rows, and today it's taking just
over
> 4 minutes to run. The other has over 60,000 rows and I'm just going to
have
> to work on limiting that severely.
> "Bruce L-C [MVP]" wrote:
> > How many fields are being returned? How many rows of data?
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > Whenever I run long SQL in VS whether it's in the Data tab or in
Preview
> > > mode, I can't seem to get a report out of it. I'm talking SQL in
excess of
> > > 200 lines.
> > >
> > > I can run the SQL fine in Query Analyzer but running it in the Data
tab,
> > it
> > > freezes VS, and when I run the Preview, the report never renders. I
have
> > even
> > > tried hardcoding all parameters, creating a stored procedure, and
running
> > the
> > > report off a view. None have resolved the issue.
> > >
> > > On a possibly related note, my connection to the database times out
> > > intermittently, saying:
> > >
> > > --
> > > Microsoft Development Environment
> > > --
> > > An error occurred while executing the query.
> > >
> > > General network error. Check your network documentation.
> > > --
> > > OK
> > > --
> > >
> > > This absolutely kills me over the course of a day. I have to shut down
VS
> > > and restart it.
> > >
> > > Is my Reporting Services VS package install corrupt? What do I do?
> >
> >
> >|||For the most part, Mr. 727 will run on the data tab, but clocks endlessly on
Preview. The report does consist of about 20 fields, but I would still expect
it to render.
Sometimes I just lose connectivity and have to close out VS. I'm not sure if
it's related, but it could be I suppose.
Any ideas?
"Bruce L-C [MVP]" wrote:
> The 727 rows should not be a problem. Is that one causing an issue from the
> data tab?
> It doesn't surprise me that the 60,000 row one has problems.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > For one report in particular, about 727 rows, and today it's taking just
> over
> > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> have
> > to work on limiting that severely.
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > How many fields are being returned? How many rows of data?
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> Preview
> > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> excess of
> > > > 200 lines.
> > > >
> > > > I can run the SQL fine in Query Analyzer but running it in the Data
> tab,
> > > it
> > > > freezes VS, and when I run the Preview, the report never renders. I
> have
> > > even
> > > > tried hardcoding all parameters, creating a stored procedure, and
> running
> > > the
> > > > report off a view. None have resolved the issue.
> > > >
> > > > On a possibly related note, my connection to the database times out
> > > > intermittently, saying:
> > > >
> > > > --
> > > > Microsoft Development Environment
> > > > --
> > > > An error occurred while executing the query.
> > > >
> > > > General network error. Check your network documentation.
> > > > --
> > > > OK
> > > > --
> > > >
> > > > This absolutely kills me over the course of a day. I have to shut down
> VS
> > > > and restart it.
> > > >
> > > > Is my Reporting Services VS package install corrupt? What do I do?
> > >
> > >
> > >
>
>|||Sometimes it runs from the data tab. Sometimes (like now), it hoses VS. The
query is 309 lines long and is pretty complex...Still, I'm having a heck of a
time. Could it be my RS client install, or could it be my machine?
"Bruce L-C [MVP]" wrote:
> The 727 rows should not be a problem. Is that one causing an issue from the
> data tab?
> It doesn't surprise me that the 60,000 row one has problems.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > For one report in particular, about 727 rows, and today it's taking just
> over
> > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> have
> > to work on limiting that severely.
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > How many fields are being returned? How many rows of data?
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> Preview
> > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> excess of
> > > > 200 lines.
> > > >
> > > > I can run the SQL fine in Query Analyzer but running it in the Data
> tab,
> > > it
> > > > freezes VS, and when I run the Preview, the report never renders. I
> have
> > > even
> > > > tried hardcoding all parameters, creating a stored procedure, and
> running
> > > the
> > > > report off a view. None have resolved the issue.
> > > >
> > > > On a possibly related note, my connection to the database times out
> > > > intermittently, saying:
> > > >
> > > > --
> > > > Microsoft Development Environment
> > > > --
> > > > An error occurred while executing the query.
> > > >
> > > > General network error. Check your network documentation.
> > > > --
> > > > OK
> > > > --
> > > >
> > > > This absolutely kills me over the course of a day. I have to shut down
> VS
> > > > and restart it.
> > > >
> > > > Is my Reporting Services VS package install corrupt? What do I do?
> > >
> > >
> > >
>
>|||Did you say you tried it as a stored procedure and you still had problems.
20 fields should not be a problem. 309 lines of a query could be a problem
in the IDE (not necessarily when deployed). I suggest try deploying it and
see if it works to determine if it is an IDE only problem. Next, try having
it in a stored procedure.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
news:0C35989D-938D-4EE6-B1F3-746130C76E80@.microsoft.com...
> Sometimes it runs from the data tab. Sometimes (like now), it hoses VS.
The
> query is 309 lines long and is pretty complex...Still, I'm having a heck
of a
> time. Could it be my RS client install, or could it be my machine?
> "Bruce L-C [MVP]" wrote:
> > The 727 rows should not be a problem. Is that one causing an issue from
the
> > data tab?
> >
> > It doesn't surprise me that the 60,000 row one has problems.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > > For one report in particular, about 727 rows, and today it's taking
just
> > over
> > > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> > have
> > > to work on limiting that severely.
> > >
> > > "Bruce L-C [MVP]" wrote:
> > >
> > > > How many fields are being returned? How many rows of data?
> > > >
> > > >
> > > > --
> > > > Bruce Loehle-Conger
> > > > MVP SQL Server Reporting Services
> > > >
> > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> > Preview
> > > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> > excess of
> > > > > 200 lines.
> > > > >
> > > > > I can run the SQL fine in Query Analyzer but running it in the
Data
> > tab,
> > > > it
> > > > > freezes VS, and when I run the Preview, the report never renders.
I
> > have
> > > > even
> > > > > tried hardcoding all parameters, creating a stored procedure, and
> > running
> > > > the
> > > > > report off a view. None have resolved the issue.
> > > > >
> > > > > On a possibly related note, my connection to the database times
out
> > > > > intermittently, saying:
> > > > >
> > > > > --
> > > > > Microsoft Development Environment
> > > > > --
> > > > > An error occurred while executing the query.
> > > > >
> > > > > General network error. Check your network documentation.
> > > > > --
> > > > > OK
> > > > > --
> > > > >
> > > > > This absolutely kills me over the course of a day. I have to shut
down
> > VS
> > > > > and restart it.
> > > > >
> > > > > Is my Reporting Services VS package install corrupt? What do I do?
> > > >
> > > >
> > > >
> >
> >
> >|||Yes, I did give it a shot as a stored procedure, with no luck.
Well, tomorrow's another day. I'll try deploying it and seeing what happens.
Thanks for the help.
Mike
"Bruce L-C [MVP]" wrote:
> Did you say you tried it as a stored procedure and you still had problems.
> 20 fields should not be a problem. 309 lines of a query could be a problem
> in the IDE (not necessarily when deployed). I suggest try deploying it and
> see if it works to determine if it is an IDE only problem. Next, try having
> it in a stored procedure.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> news:0C35989D-938D-4EE6-B1F3-746130C76E80@.microsoft.com...
> > Sometimes it runs from the data tab. Sometimes (like now), it hoses VS.
> The
> > query is 309 lines long and is pretty complex...Still, I'm having a heck
> of a
> > time. Could it be my RS client install, or could it be my machine?
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > The 727 rows should not be a problem. Is that one causing an issue from
> the
> > > data tab?
> > >
> > > It doesn't surprise me that the 60,000 row one has problems.
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > > > For one report in particular, about 727 rows, and today it's taking
> just
> > > over
> > > > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> > > have
> > > > to work on limiting that severely.
> > > >
> > > > "Bruce L-C [MVP]" wrote:
> > > >
> > > > > How many fields are being returned? How many rows of data?
> > > > >
> > > > >
> > > > > --
> > > > > Bruce Loehle-Conger
> > > > > MVP SQL Server Reporting Services
> > > > >
> > > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> > > Preview
> > > > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> > > excess of
> > > > > > 200 lines.
> > > > > >
> > > > > > I can run the SQL fine in Query Analyzer but running it in the
> Data
> > > tab,
> > > > > it
> > > > > > freezes VS, and when I run the Preview, the report never renders.
> I
> > > have
> > > > > even
> > > > > > tried hardcoding all parameters, creating a stored procedure, and
> > > running
> > > > > the
> > > > > > report off a view. None have resolved the issue.
> > > > > >
> > > > > > On a possibly related note, my connection to the database times
> out
> > > > > > intermittently, saying:
> > > > > >
> > > > > > --
> > > > > > Microsoft Development Environment
> > > > > > --
> > > > > > An error occurred while executing the query.
> > > > > >
> > > > > > General network error. Check your network documentation.
> > > > > > --
> > > > > > OK
> > > > > > --
> > > > > >
> > > > > > This absolutely kills me over the course of a day. I have to shut
> down
> > > VS
> > > > > > and restart it.
> > > > > >
> > > > > > Is my Reporting Services VS package install corrupt? What do I do?
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||Have you tried changing the connection string of the data source to increase
the time out?
try
"data source=ServerName;initial catalog=DatabaseName;Connection Timeout=30"
The connection timeout has a default of 15.
"Bassist695" wrote:
> Yes, I did give it a shot as a stored procedure, with no luck.
> Well, tomorrow's another day. I'll try deploying it and seeing what happens.
> Thanks for the help.
> Mike
> "Bruce L-C [MVP]" wrote:
> > Did you say you tried it as a stored procedure and you still had problems.
> > 20 fields should not be a problem. 309 lines of a query could be a problem
> > in the IDE (not necessarily when deployed). I suggest try deploying it and
> > see if it works to determine if it is an IDE only problem. Next, try having
> > it in a stored procedure.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > news:0C35989D-938D-4EE6-B1F3-746130C76E80@.microsoft.com...
> > > Sometimes it runs from the data tab. Sometimes (like now), it hoses VS.
> > The
> > > query is 309 lines long and is pretty complex...Still, I'm having a heck
> > of a
> > > time. Could it be my RS client install, or could it be my machine?
> > >
> > > "Bruce L-C [MVP]" wrote:
> > >
> > > > The 727 rows should not be a problem. Is that one causing an issue from
> > the
> > > > data tab?
> > > >
> > > > It doesn't surprise me that the 60,000 row one has problems.
> > > >
> > > >
> > > > --
> > > > Bruce Loehle-Conger
> > > > MVP SQL Server Reporting Services
> > > >
> > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > > > > For one report in particular, about 727 rows, and today it's taking
> > just
> > > > over
> > > > > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> > > > have
> > > > > to work on limiting that severely.
> > > > >
> > > > > "Bruce L-C [MVP]" wrote:
> > > > >
> > > > > > How many fields are being returned? How many rows of data?
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Bruce Loehle-Conger
> > > > > > MVP SQL Server Reporting Services
> > > > > >
> > > > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> > > > Preview
> > > > > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> > > > excess of
> > > > > > > 200 lines.
> > > > > > >
> > > > > > > I can run the SQL fine in Query Analyzer but running it in the
> > Data
> > > > tab,
> > > > > > it
> > > > > > > freezes VS, and when I run the Preview, the report never renders.
> > I
> > > > have
> > > > > > even
> > > > > > > tried hardcoding all parameters, creating a stored procedure, and
> > > > running
> > > > > > the
> > > > > > > report off a view. None have resolved the issue.
> > > > > > >
> > > > > > > On a possibly related note, my connection to the database times
> > out
> > > > > > > intermittently, saying:
> > > > > > >
> > > > > > > --
> > > > > > > Microsoft Development Environment
> > > > > > > --
> > > > > > > An error occurred while executing the query.
> > > > > > >
> > > > > > > General network error. Check your network documentation.
> > > > > > > --
> > > > > > > OK
> > > > > > > --
> > > > > > >
> > > > > > > This absolutely kills me over the course of a day. I have to shut
> > down
> > > > VS
> > > > > > > and restart it.
> > > > > > >
> > > > > > > Is my Reporting Services VS package install corrupt? What do I do?
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||No, I haven't tried that. I don't believe the queries are timing out.
Wouldn't I get an error message to indicate that?
At present, there is no timeout set, which I believe means that the query
will not time out.
I'm going to try the deploy-and-see method...Let's hope it's my IDE.
Mike
"Carl Finnegan" wrote:
> Have you tried changing the connection string of the data source to increase
> the time out?
> try
> "data source=ServerName;initial catalog=DatabaseName;Connection Timeout=30"
> The connection timeout has a default of 15.
> "Bassist695" wrote:
> > Yes, I did give it a shot as a stored procedure, with no luck.
> >
> > Well, tomorrow's another day. I'll try deploying it and seeing what happens.
> > Thanks for the help.
> >
> > Mike
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > Did you say you tried it as a stored procedure and you still had problems.
> > > 20 fields should not be a problem. 309 lines of a query could be a problem
> > > in the IDE (not necessarily when deployed). I suggest try deploying it and
> > > see if it works to determine if it is an IDE only problem. Next, try having
> > > it in a stored procedure.
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > news:0C35989D-938D-4EE6-B1F3-746130C76E80@.microsoft.com...
> > > > Sometimes it runs from the data tab. Sometimes (like now), it hoses VS.
> > > The
> > > > query is 309 lines long and is pretty complex...Still, I'm having a heck
> > > of a
> > > > time. Could it be my RS client install, or could it be my machine?
> > > >
> > > > "Bruce L-C [MVP]" wrote:
> > > >
> > > > > The 727 rows should not be a problem. Is that one causing an issue from
> > > the
> > > > > data tab?
> > > > >
> > > > > It doesn't surprise me that the 60,000 row one has problems.
> > > > >
> > > > >
> > > > > --
> > > > > Bruce Loehle-Conger
> > > > > MVP SQL Server Reporting Services
> > > > >
> > > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > > news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > > > > > For one report in particular, about 727 rows, and today it's taking
> > > just
> > > > > over
> > > > > > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> > > > > have
> > > > > > to work on limiting that severely.
> > > > > >
> > > > > > "Bruce L-C [MVP]" wrote:
> > > > > >
> > > > > > > How many fields are being returned? How many rows of data?
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Bruce Loehle-Conger
> > > > > > > MVP SQL Server Reporting Services
> > > > > > >
> > > > > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > > > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > > > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> > > > > Preview
> > > > > > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> > > > > excess of
> > > > > > > > 200 lines.
> > > > > > > >
> > > > > > > > I can run the SQL fine in Query Analyzer but running it in the
> > > Data
> > > > > tab,
> > > > > > > it
> > > > > > > > freezes VS, and when I run the Preview, the report never renders.
> > > I
> > > > > have
> > > > > > > even
> > > > > > > > tried hardcoding all parameters, creating a stored procedure, and
> > > > > running
> > > > > > > the
> > > > > > > > report off a view. None have resolved the issue.
> > > > > > > >
> > > > > > > > On a possibly related note, my connection to the database times
> > > out
> > > > > > > > intermittently, saying:
> > > > > > > >
> > > > > > > > --
> > > > > > > > Microsoft Development Environment
> > > > > > > > --
> > > > > > > > An error occurred while executing the query.
> > > > > > > >
> > > > > > > > General network error. Check your network documentation.
> > > > > > > > --
> > > > > > > > OK
> > > > > > > > --
> > > > > > > >
> > > > > > > > This absolutely kills me over the course of a day. I have to shut
> > > down
> > > > > VS
> > > > > > > > and restart it.
> > > > > > > >
> > > > > > > > Is my Reporting Services VS package install corrupt? What do I do?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >

logon window

Hi,
Whenever I click on a report to open it, it asks me for my Windows user ID
and password. I am connected to my desktop using my domain account and
report server is installed on SQL Server (domain controller as well).
The report is using NT authentication method.
Does anybody know how can I get rid of the login information window?
ThanksHi,
If You are using a shared datasource then rightclick on the datasource
->open
In the credentials tab check what is the option selected it should be "Use
Windows Authentication(integrated security)" If you have windows
authentication for you Sql server. If the option selected in this tab is
"Prompt for credentials" then the report promt for user credentials every
time it launches.
Incase u are not using shared datasource then u canget the above tab from
the data tab of the reportdesigner and then browsing on the datasource
dropdown.
Leme know if this solves ur problem
Thanks,
siaj
"Alex" wrote:
> Hi,
> Whenever I click on a report to open it, it asks me for my Windows user ID
> and password. I am connected to my desktop using my domain account and
> report server is installed on SQL Server (domain controller as well).
> The report is using NT authentication method.
> Does anybody know how can I get rid of the login information window?
> Thanks
>
>|||Make sure that your IE and IIS settings are correct. Within IE go to tools
internet options and then security. You will want to make sure the RS web
site is in your local intranet zone. Once it is there, make sure that the
"User Authentication" section of the settings are set to "Automatic logon
with current username and password." This tells IE to send the username and
password to the server. On IIS make sure that "Integrated Windows
authentication" is checked for the web site and uncheck the remaining boxes.
"Alex" wrote:
> Hi,
> Whenever I click on a report to open it, it asks me for my Windows user ID
> and password. I am connected to my desktop using my domain account and
> report server is installed on SQL Server (domain controller as well).
> The report is using NT authentication method.
> Does anybody know how can I get rid of the login information window?
> Thanks
>
>|||Thanks. This one solved my problem.
"MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
news:11CE3B20-F0A0-4A9C-84D2-2DDDA6B3C226@.microsoft.com...
> Make sure that your IE and IIS settings are correct. Within IE go to tools
> internet options and then security. You will want to make sure the RS web
> site is in your local intranet zone. Once it is there, make sure that the
> "User Authentication" section of the settings are set to "Automatic logon
> with current username and password." This tells IE to send the username
and
> password to the server. On IIS make sure that "Integrated Windows
> authentication" is checked for the web site and uncheck the remaining
boxes.
>
> "Alex" wrote:
> > Hi,
> >
> > Whenever I click on a report to open it, it asks me for my Windows user
ID
> > and password. I am connected to my desktop using my domain account and
> > report server is installed on SQL Server (domain controller as well).
> > The report is using NT authentication method.
> > Does anybody know how can I get rid of the login information window?
> >
> > Thanks
> >
> >
> >|||I have the same problem... and tried your suggestions with no luck.
Administrators and users can browse the Reports application. Administrators
can view the reports, but users get an authentication prompt.
Both the Reports and ReportServer application use Windows Integrated Auth
and have Anonymous disabled.
What would the difference be if the user can view Reports but not
ReportServer? (I tried https://{server}/ReportServer and still got the prompt)
There's got to be some difference between
"Alex" wrote:
> Thanks. This one solved my problem.
> "MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
> news:11CE3B20-F0A0-4A9C-84D2-2DDDA6B3C226@.microsoft.com...
> > Make sure that your IE and IIS settings are correct. Within IE go to tools
> > internet options and then security. You will want to make sure the RS web
> > site is in your local intranet zone. Once it is there, make sure that the
> > "User Authentication" section of the settings are set to "Automatic logon
> > with current username and password." This tells IE to send the username
> and
> > password to the server. On IIS make sure that "Integrated Windows
> > authentication" is checked for the web site and uncheck the remaining
> boxes.
> >
> >
> > "Alex" wrote:
> >
> > > Hi,
> > >
> > > Whenever I click on a report to open it, it asks me for my Windows user
> ID
> > > and password. I am connected to my desktop using my domain account and
> > > report server is installed on SQL Server (domain controller as well).
> > > The report is using NT authentication method.
> > > Does anybody know how can I get rid of the login information window?
> > >
> > > Thanks
> > >
> > >
> > >
>
>|||I had to set up the user/group in question with permissions to Reports and
ReportServer in IIS.
"Peter Capazzi" wrote:
> I have the same problem... and tried your suggestions with no luck.
> Administrators and users can browse the Reports application. Administrators
> can view the reports, but users get an authentication prompt.
> Both the Reports and ReportServer application use Windows Integrated Auth
> and have Anonymous disabled.
> What would the difference be if the user can view Reports but not
> ReportServer? (I tried https://{server}/ReportServer and still got the prompt)
> There's got to be some difference between
> "Alex" wrote:
> > Thanks. This one solved my problem.
> >
> > "MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
> > news:11CE3B20-F0A0-4A9C-84D2-2DDDA6B3C226@.microsoft.com...
> > > Make sure that your IE and IIS settings are correct. Within IE go to tools
> > > internet options and then security. You will want to make sure the RS web
> > > site is in your local intranet zone. Once it is there, make sure that the
> > > "User Authentication" section of the settings are set to "Automatic logon
> > > with current username and password." This tells IE to send the username
> > and
> > > password to the server. On IIS make sure that "Integrated Windows
> > > authentication" is checked for the web site and uncheck the remaining
> > boxes.
> > >
> > >
> > > "Alex" wrote:
> > >
> > > > Hi,
> > > >
> > > > Whenever I click on a report to open it, it asks me for my Windows user
> > ID
> > > > and password. I am connected to my desktop using my domain account and
> > > > report server is installed on SQL Server (domain controller as well).
> > > > The report is using NT authentication method.
> > > > Does anybody know how can I get rid of the login information window?
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> >
> >
> >

Logon failure?

Hello,
We just installed SQL Server developer's edition on a new Windows XP Pro
workstation. But whenever we bring up the SQL Server service manager, and
click Start, we get the error:
"The service did not start due to logon failure"
When we did the install, we left the "sa" password blank, and we're using
SQL Server authentication. Can anyone say what might be wrong?
Thanks!!
It's most likely the Windows account that starts up the SQL Server
service. The password is probably expired. Check your SQL
Server Service log on credentials
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL Server developer's edition on a new Windows XP Pro
> workstation. But whenever we bring up the SQL Server service manager, and
> click Start, we get the error:
> "The service did not start due to logon failure"
> When we did the install, we left the "sa" password blank, and we're using
> SQL Server authentication. Can anyone say what might be wrong?
> Thanks!!
>
|||Oh, by the way... USE A STRONG PASSWORD FOR 'sa'!!!!
Don't use blanks; a lot of SQL Server exploits use a brute force method
to compromise a system. They'll check for passwords such 'sa' or blank.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL Server developer's edition on a new Windows XP Pro
> workstation. But whenever we bring up the SQL Server service manager, and
> click Start, we get the error:
> "The service did not start due to logon failure"
> When we did the install, we left the "sa" password blank, and we're using
> SQL Server authentication. Can anyone say what might be wrong?
> Thanks!!
>
|||Oh yes, for server deployments of SQL Server, we always use strong
passwords, but the workstation in question is at a home office, and not
connected to the Internet. Thanks!
"Armando Prato" <aprato@.REMOVEMEkronos.com> wrote in message
news:O#ZOgN1dFHA.3836@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Oh, by the way... USE A STRONG PASSWORD FOR 'sa'!!!!
> Don't use blanks; a lot of SQL Server exploits use a brute force method
> to compromise a system. They'll check for passwords such 'sa' or blank.
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
and[vbcol=seagreen]
using
>

Logon failure?

Hello,
We just installed SQL Server developer's edition on a new Windows XP Pro
workstation. But whenever we bring up the SQL Server service manager, and
click Start, we get the error:
"The service did not start due to logon failure"
When we did the install, we left the "sa" password blank, and we're using
SQL Server authentication. Can anyone say what might be wrong?
Thanks!!It's most likely the Windows account that starts up the SQL Server
service. The password is probably expired. Check your SQL
Server Service log on credentials
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL Server developer's edition on a new Windows XP Pro
> workstation. But whenever we bring up the SQL Server service manager, and
> click Start, we get the error:
> "The service did not start due to logon failure"
> When we did the install, we left the "sa" password blank, and we're using
> SQL Server authentication. Can anyone say what might be wrong?
> Thanks!!
>|||Oh, by the way... USE A STRONG PASSWORD FOR 'sa'!!!!
Don't use blanks; a lot of SQL Server exploits use a brute force method
to compromise a system. They'll check for passwords such 'sa' or blank.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL Server developer's edition on a new Windows XP Pro
> workstation. But whenever we bring up the SQL Server service manager, and
> click Start, we get the error:
> "The service did not start due to logon failure"
> When we did the install, we left the "sa" password blank, and we're using
> SQL Server authentication. Can anyone say what might be wrong?
> Thanks!!
>|||Oh yes, for server deployments of SQL Server, we always use strong
passwords, but the workstation in question is at a home office, and not
connected to the Internet. Thanks!
"Armando Prato" <aprato@.REMOVEMEkronos.com> wrote in message
news:O#ZOgN1dFHA.3836@.tk2msftngp13.phx.gbl...
> Oh, by the way... USE A STRONG PASSWORD FOR 'sa'!!!!
> Don't use blanks; a lot of SQL Server exploits use a brute force method
> to compromise a system. They'll check for passwords such 'sa' or blank.
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL Server developer's edition on a new Windows XP Pro
> > workstation. But whenever we bring up the SQL Server service manager,
and
> > click Start, we get the error:
> >
> > "The service did not start due to logon failure"
> >
> > When we did the install, we left the "sa" password blank, and we're
using
> > SQL Server authentication. Can anyone say what might be wrong?
> >
> > Thanks!!
> >
> >
>

Logon failure?

Hello,
We just installed SQL Server developer's edition on a new Windows XP Pro
workstation. But whenever we bring up the SQL Server service manager, and
click Start, we get the error:
"The service did not start due to logon failure"
When we did the install, we left the "sa" password blank, and we're using
SQL Server authentication. Can anyone say what might be wrong?
Thanks!!It's most likely the Windows account that starts up the SQL Server
service. The password is probably expired. Check your SQL
Server Service log on credentials
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL Server developer's edition on a new Windows XP Pro
> workstation. But whenever we bring up the SQL Server service manager, and
> click Start, we get the error:
> "The service did not start due to logon failure"
> When we did the install, we left the "sa" password blank, and we're using
> SQL Server authentication. Can anyone say what might be wrong?
> Thanks!!
>|||Oh, by the way... USE A STRONG PASSWORD FOR 'sa'!!!!
Don't use blanks; a lot of SQL Server exploits use a brute force method
to compromise a system. They'll check for passwords such 'sa' or blank.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL Server developer's edition on a new Windows XP Pro
> workstation. But whenever we bring up the SQL Server service manager, and
> click Start, we get the error:
> "The service did not start due to logon failure"
> When we did the install, we left the "sa" password blank, and we're using
> SQL Server authentication. Can anyone say what might be wrong?
> Thanks!!
>|||Oh yes, for server deployments of SQL Server, we always use strong
passwords, but the workstation in question is at a home office, and not
connected to the Internet. Thanks!
"Armando Prato" <aprato@.REMOVEMEkronos.com> wrote in message
news:O#ZOgN1dFHA.3836@.tk2msftngp13.phx.gbl...
> Oh, by the way... USE A STRONG PASSWORD FOR 'sa'!!!!
> Don't use blanks; a lot of SQL Server exploits use a brute force method
> to compromise a system. They'll check for passwords such 'sa' or blank.
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
and[vbcol=seagreen]
using[vbcol=seagreen]
>

Login to SQL Server management studio

Hi,

I am facing a strange behavior during loging in to SQL server mangement studio.

Whenever I install SQL server express, various protocols like Named Pipe and TCP/IP and SQL browser are disabled by default. But still I am able to log in to SQL Server throguh Management studio.

But when I try to log in to SQL server throguh one of my applications, it allows me to log in to it only for one time. From next time onwards, I am not able to log in to SQL server neither through my application nor through Management studio.

I connect to SQL server using "machine name"\"Instance name". Machine name is the name of machine on my office LAN.

PS: Once this problem occurs, I can log in to SQL server if I use "localhost" instead of "machine name".

Any suggestions would be tremendously helpful.

Regards

-Orion

SQL Express supports connecting through Shared Memory, which is a local connectivity protocol that is used by the SQL Native Client. This is how you're connecting with Management Studio. I can't tell you what the problem is with your application as you have not provided an error message or error log.

Mike

|||

Hi Mike,

Thanks for the reply.

>>
I can't tell you what the problem is with your application as you have not provided an error message or error log
>>

Following are the details of the exception thrown by SQL server.

{"State:08001,Native:6,Origin:[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] State:01000,Native:11004,Origin:[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]"}

The problem is when it allows my application to connect to SQL Server only once. After this, I need to enable TCP/IP protocol for any subsequent connection through my application or SQL Server management studio.

Regards,
Orion

|||

Hi Orion,

Could you define what you mean by "subsequent connections through my application"? Are you talking about a single application creating multiple threads connecting to SQL Server? Are these different copies of the same application being run by other users on other computers? What is the connection string you're using from your application?

I don't recognize that error, is there any more descirptive text?

Mike