Saturday, February 25, 2012

Problem with Performances

Hallo everbody,
I'm having a serious problem with my aspx pages. Ideveloped few pages that allow users to retrieve books information froma database (MS SQL). The database table contains about 5000 records.
My queries are very simple, nevertheless the time necessary to perform them is extremely long.
I tried to set the time out of the data adapter to 0 and I removed thedebug mode (debug="true") from the web.config file. I'm still not ableto perform a query.
What is wrong with it? Is it something related with the database?

Any help is appreciated...

Thanks,

christianIt does not seem to be a database issue. You can execute the query in Query Analyzer(SQL2000)/Management Studio(SQL2005) and see how long will it take to complete. However would you show me the query statement and your table schema?|||This si the query:
SELECT *
FROM DocTable1 WHERE FREETEXT("column name",column value)
(very simple)

The table is

CREATE TABLE [DocTable1] (
[DocNumber] [int] NOT NULL ,
[LastName] [varchar] (50) ,
[FirstName] [varchar] (50) ,
[Program] [varchar] (50) ,
[Paper] [varchar] (50) ,
[Location] [varchar] (50) ,
[ANNO] [int] NULL ,
[Title] [ntext] ,
[TitleSort] [ntext] ,
[Keywords] [ntext] ,
[FT] [char] (1) ,
[URL] [varchar] (250) ,
CONSTRAINT [PK_DocTable1] PRIMARY KEY CLUSTERED
(
[DocNumber]
) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO|||

When FREETEXT is used, the full-text query engine internally "word-breaks" thefreetext_stringinto a number of search terms and assigns each term a weight and then finds the matches. So it can cause poor performance if the searched column contains a large text. You can create full-text indexes on the table to speed up full-text query: To enable a database for full-text indexing:
1. Expand a server group, and then expand a server.
2. Expand Databases, and then click a database to enable.
3. On the Tools menu, click Full-Text Indexing.
4. Complete the Full-Text Indexing Wizard.

Search full-text indexes in SQL2000 Books Online you'll find lots of articles.

|||Thanks for your suggestion, but I have already done that.
The problem is the CLR debugger. I'm using just the debugger, I do not have Visual Studio.
In order to use the debugger you have to change the we.config file,adding a line debug="true" which set the asp.net framework to work indebug mode. This slowed down incredibly the performances of the entirewebsite. I removed the debugger, I delete the line debug="true" in theweb.config file and the site went back tyo work perfectly.

christian|||Good news:) I've learned much from you. Thanks!

No comments:

Post a Comment