blocks hangup database when inserting in 1 specific table

Hi,

We use a database with about 40 related tables. Some tables contain as
much as 30.000 records. We use Access97 as an interface to the
database. Now recently we have the problem that when we want to insert
a row in one specific table (alwasy the same) the database makes
blocks.

Details:
- about 10% of the data was inserted using copying from Excel, before
this action there was no problem, though there is no evidence that
this causes the problem.
- inserting rows via the Query Analyzer works fine, via Access causes
trouble.
- the tempdb lofile has grown to 48Mb.

Has anyone ideas about what is going on and what I can do to solve the
problem?

TAV,
Jan WillemsJan Willems (jwillems@.xs4all.nl) writes:
> We use a database with about 40 related tables. Some tables contain as
> much as 30.000 records. We use Access97 as an interface to the
> database. Now recently we have the problem that when we want to insert
> a row in one specific table (alwasy the same) the database makes
> blocks.

"Makes blocks"? You mean that the INSERT operation is blocked, and you
have to cancel the operation to continue?

When the situation occurs, use sp_who from Query Analyzer, and see if
any process has a non-zero value in the Blk column. In such case, the
process listed in Blk, blocks the spid of that row.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

blank pages in reports through subscriptions

I have Reporting Services 2005 wsp1, SQL Server 2005 version 9.00.2047. When
I generate reports through Reports Admin interface and then export them to
PDF, they come out ok. When I set up a subscription that is supposed to send
a report in pdf format - I get the same report with around 50 blank pages
inserted in it.
Anybody ran across the same stuff?On Mar 2, 11:39 am, "ilona" <ilona_scramb...@.no-go.com> wrote:
> I have Reporting Services 2005 wsp1, SQL Server 2005 version 9.00.2047. When
> I generate reports through Reports Admin interface and then export them to
> PDF, they come out ok. When I set up a subscription that is supposed to send
> a report in pdf format - I get the same report with around 50 blank pages
> inserted in it.
> Anybody ran across the same stuff?
I've had some problems with this before...I would try to eliminate any
unused space in the report designer area and check your page
setting...
Cheers,
-Ben

Blank Page Between Exported Report

For some reason when I export the report from the web interface it exports
with an extra page between each page - it looks as if it has set the tables
that are in the report to 100% and then added an extra page because it
overflowed. However, this does not occur when I export from the Report
Manager or from the report Toolkit IDE.
Any ideas?
MikeTake a look at the previous post on this:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=4da98d7c-af5a-45c0-8cdf-dad47c6cb771
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Solomons" <mikesolo@.optonline.net> wrote in message
news:uVWw5ZKdEHA.1040@.TK2MSFTNGP10.phx.gbl...
> For some reason when I export the report from the web interface it exports
> with an extra page between each page - it looks as if it has set the
tables
> that are in the report to 100% and then added an extra page because it
> overflowed. However, this does not occur when I export from the Report
> Manager or from the report Toolkit IDE.
> Any ideas?
> Mike
>|||That didn't solve my problem - it's really odd - like I said in the IDE when
I export to PDF it fits fine, but when I use the Report Viewer ASP.NET
component from the web it adds an extra space - it also looks like the table
has been set to strectch 100% or something - any other ideas?
Mike
"Ravi Mumulla (Microsoft)" <ravimu@.online.microsoft.com> wrote in message
news:ulG1p0KdEHA.2268@.TK2MSFTNGP12.phx.gbl...
> Take a look at the previous post on this:
>
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=4da98d7c-af5a-45c0-8cdf-dad47c6cb771
> --
> Ravi Mumulla (Microsoft)
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Michael Solomons" <mikesolo@.optonline.net> wrote in message
> news:uVWw5ZKdEHA.1040@.TK2MSFTNGP10.phx.gbl...
> > For some reason when I export the report from the web interface it
exports
> > with an extra page between each page - it looks as if it has set the
> tables
> > that are in the report to 100% and then added an extra page because it
> > overflowed. However, this does not occur when I export from the Report
> > Manager or from the report Toolkit IDE.
> >
> > Any ideas?
> >
> > Mike
> >
> >
>|||Encountered a similar problem where;
"Report Properties, Layout, Page width=8.5 Page height=11"
and
"Body Properties, Size, width=8.5, height=11"
Exported PDF's printed extra pages. After trying near everthing I could
think of I changed the height as follows;
"Body Properties, Size, width=8.5, height=10.99"
After that everything worked just fine.
Go figure, but it worked.
HTH,
Greg|||Nope - didn't work - anothe rodd thing though - I have an image which is
psuhed to the furthemost right side of the report - in the design view, it
is the item which is right most - when publish to the web and view it in the
report viewer, it is stilll all the way to the right, but the table seems to
go much further - as if that is the problem.
Also - keep in mind this isn't happening when I export to PDF from the
Report Manager interface, only when I export from the report viewer ASP.net
component from our website.
Odd...
Mike
"Greg Rowland" <greg@.waveltd.com> wrote in message
news:%23PeuB0LdEHA.3664@.TK2MSFTNGP12.phx.gbl...
> Encountered a similar problem where;
> "Report Properties, Layout, Page width=8.5 Page height=11"
> and
> "Body Properties, Size, width=8.5, height=11"
> Exported PDF's printed extra pages. After trying near everthing I could
> think of I changed the height as follows;
> "Body Properties, Size, width=8.5, height=10.99"
> After that everything worked just fine.
> Go figure, but it worked.
> HTH,
> Greg
>|||You may want to try exporting to a PDF or other format, just see what it
looks like. You may get some other ideas from that.
Good luck,
G