Connectivity with sql server

The problem what iam facing,is while updating records from
a network system to sql server,the time taken is very high.
I would like to know how to make faster updation of record
to my sql database.
And what role does ODBC play here.and is there any log
file or temporary files created at server end,if i would
like to know the path.and does it got to do anything with
the record updation speed.
I would be a great help for me...!!What type of update are you doing? Is this a one-time thing or a
continuously needed update? What is your table structure, what does your
update statement look like? Do you have indexes on the table? What recovery
mode are you running the database in? How many users are connected to the
server when you run this update? Are there any locking/blocking issues? Lots
of questions, answer them and I'm sure someone can help.
Ray Higdon MCSE, MCDBA, CCNA
--
"ssd" <ssd_myworld@.yahoo.com.sg> wrote in message
news:0e8e01c3deff$e7afc9f0$a601280a@.phx.gbl...

quote:

---

> The problem what iam facing,is while updating records from
> a network system to sql server,the time taken is very high.
> I would like to know how to make faster updation of record
> to my sql database.
> And what role does ODBC play here.and is there any log
> file or temporary files created at server end,if i would
> like to know the path.and does it got to do anything with
> the record updation speed.
> I would be a great help for me...!!

---

|||I got one sql server connected to 5 workstations,A small
vb application which updates 10-15 fileds,submission of
each record is taking 35-40secs,we will be updating 50
records at a time span of 30-45 minutes.
Here the time taken to update each record is pain taking.
How can i over come this problem inorder to submit my
records faster.
And ODBC got to do anything at workstation end,i mean we
got to configure ODBC at workstation.sqlsql

Connectivity between vb 6.0 and Sql server 2000 (data base is in Server)

Hai all
I am sudhir
I am facing problem to establish connection between vb 6.0 and ms sql
server 2000, ie data base is in Server. I want to make conneciton
between them.
please help me.
Advance thank you alll
' Basic ADO
Dim strConnectionString as String
Dim myConn as ADODB.Connection
Dim myRS as ADODB.Recordset
' This uses the SA username, but you can create / use another
strConnectionString = "Provider=SQLOLEDB.1;Password=MySAPassword;Dat a
Source=MyServerName;User ID=SA;Initial Catalog=MyDBName;"
Set myConn = New ADODB.Connection
myConn.Open strConnectionString
set myRS = myConn.Execute "SELECT MyCol From MyTable"
If not myRS.EOF then
myRS.MoveFirst
While Not myRS.EOF
' Read stuff out of the recordset
Msgbox mrRS!MyCol
mrRS.MoveNext
Wend
End If
Jamie Clancy
Ulysses Systems, London
"sudhir9992003@.gmail.com" wrote:

> Hai all
> I am sudhir
> I am facing problem to establish connection between vb 6.0 and ms sql
> server 2000, ie data base is in Server. I want to make conneciton
> between them.
> please help me.
> Advance thank you alll
>

Connection problem with ODBC to MSDE

Dear Friends
I am facing problem to connect to the SQL server which is in the network
through ODBC. I can ping to the machine all shares are available but not abl
e
to get the ODBC connection with SQL. Please suggest what can be the reason
and how i can solve the same.
Best regards
ShaileshHi
You may have installed MSDE with DISABLENETWORKPROTOCOLS=1 which does not
enable the network protocols. In which case you should still be able to
connect to the server on the machine itself. You can enable them by running
the command utility svrnetcn.exe
John
"Sharad2005" wrote:

> Dear Friends
> I am facing problem to connect to the SQL server which is in the network
> through ODBC. I can ping to the machine all shares are available but not a
ble
> to get the ODBC connection with SQL. Please suggest what can be the reason
> and how i can solve the same.
> Best regards
> Shailesh

Connection Problem

Hi,
I'm facing on my local machine (Windows 2000 advance server + SQL Server 7.0). its a site in asp.net. sometimes i recieve the message that connection timedout. When i check the number of connections in Performance Monitor, they had reached the max size of 100.

I think my problem lies in connections that remain open after the page is loaded. For example whenever I run a particular page(that shows a complex report), 14 more connections are added to User Connections in Performance Monitor.
Can anyone tell me why the connections remain open even after the page is executed? Shouldn't they be closed once the page is loaded and returned to the connection pool to be reused?

Any help/suggestion will be highly appreciated.

ThanksThey should. Can you show us the connection string you use? Also are you closing the command when you are finished? I use Microsoft Data Access Application Blocks to handle this, and most of the closing etc. is taken care of in that code.|||thanks for the quick response.

Here is the connection string that i have in my web.config file:

<appSettings>
<add key="DB" value="server='P4'; user id='sa'; password=''; database='myDB'" /
I'm not closing the command but i'm closing the connections:

MyCommand.Connection.Close()

what do you think?|||Hi,

I added the following to my connection string "pooling=false" and it seems to have solved the problem. Performance Monitor shows that connections to database are freed when a new request is recieved by the server.

But I have read that "pooling=false" is not recommended by microsoft!!! Can someone please shed some light on this.

Thanks|||I know I've set pooling to false for one application, and it has not been a problem. This is an intranet application and I had to do this because the application was failing occaisionally. Turning pooling off turned out to be the simplest way to fix it.

I think scalability is the reason that microsoft does not recommend this. Since our application is admin app that's only going to be used by maximum 10 people, that's not an issue. HTH|||Thanks for the information. Can you give me some link to any resource related to the use of connection pooling since my application is suppose to be used by users all over the world.