ExecuteReader taking time, not in SQL server?

Question

I am executing stored procedure using ExcuteReader() command. If I execute Stored Procedure in SQL server it is taking 2 secs. But in code taking around 2 mins. I tried DataAdapter.Fill(). Still the same.

What is wrong in the code?

        spString = "usp_graph"
        sqlcmd_q.Connection = sqlCnn
        sqlcmd_q.CommandText = spString
        sqlcmd_q.CommandType = CommandType.StoredProcedure
        sqlcmd_q.Parameters.AddWithValue("@clientid", clientId)
        sqlcmd_q.Parameters.AddWithValue("@store", storeID)
        sqlcmd_q.Parameters.AddWithValue("@attributes", attributeNumber)
        sqlcmd_q.Parameters.AddWithValue("@attri1_idx", attribute1_idx)sqlCnn.Open()
        sqlcmd_q.CommandTimeout = 300

        sqldr = sqlcmd_q.ExecuteReader() // taking time here
        dt.Load(sqldr)
        dsGrid.Tables.Add(dt)

Are you doing anything like set dateformat in your stored proc? I've come across stored procs with a set dateformat slowing things down, yet it will run fine in SSMS when the query is cached. — frusDev
– frusDev, Commented Jun 2, 2011 at 20:43

Remus Rusanu · Accepted Answer · 2011-06-02 20:45:00Z

5

Slow in the Application, Fast in SSMS?. Everything you need to know about this subject, and more.

answered Jun 2, 2011 at 20:45

Remus Rusanu

296k42 gold badges459 silver badges583 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

ExecuteReader taking time, not in SQL server?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related