Viewing 15 posts - 31 through 45 (of 99 total)
Nope, I always login with same LAN ID. This problem seeems also hit 2 of my colleagues,
July 16, 2004 at 9:00 am
I tend to agree with what Alan stated. SQL server suppose to handle the resource efficiently.You should find the root cause of the slow down.
I personal really can't find any...
July 16, 2004 at 8:46 am
Several possible reason cause this error.
1. memory fragment
2. memory leak
You need track down which one is the root cause of the problem is leak or fragment, first. Then, find what...
July 16, 2004 at 8:38 am
How is data loaded ? Are they loaded thru. bcp or bulk insert ? Is there any constraints or trigger on the target table ?
June 22, 2004 at 6:49 am
We had 1 SQL had same thing. What I do is write up some sql to monitor deadlock, blocking, ... and run as a SQL job on the remote server. It...
June 18, 2004 at 9:42 am
We beta this few months ago. We compare NAS (from Network Appliance), FCAL (Fibre, IBM), and SCSI-3 solution as infrastructure guideline.
FCAL outperform the others by at least 2 folds (in...
June 16, 2004 at 7:28 am
I'll run defrag first (include index) then DB shrink.
June 15, 2004 at 8:46 am
I don't know there is a way to shrink individual table. You may need shrink the DB.
June 15, 2004 at 8:02 am
I'm not but one of my friend is. he think someone enjoy it. If you don't mind travel a lot and always under some fire (on the client site). You...
June 11, 2004 at 2:06 pm
I think 2GB limitation is on standard edition
June 4, 2004 at 12:23 pm
One more thing I forgot to mention.
Make sure connection are properly closed. I found a lot of ASP developers do not close the connection and release the memory correctly. This...
June 4, 2004 at 7:28 am
SQL 2K seems not too bad to manage memory. Nost of the time, the memory was eaten up by
1. un-closed cursor (use profiler to identify)
2. jdbc driver (you need apply...
June 4, 2004 at 7:16 am
The other thoughts.
Microsoft specfic say
DO NOT
1. install anti-virus on the SQL server
2. install disk keeper or alike
both are using kernnel space and could interfere with SQL server.
June 3, 2004 at 10:17 am
My experience with SQL not relasing memory are
1. not close cursors
2. using jdbc driver
3. using OA_* extended proc.
Take a look any of this happen to you. Not closed cursors...
June 3, 2004 at 10:14 am
Do you do disk backup on your shop ? Is the disk backup (or network backup). somehow hung casue you the problem ?
June 2, 2004 at 9:19 am
Viewing 15 posts - 31 through 45 (of 99 total)