Viewing 15 posts - 361 through 375 (of 605 total)
Hi,
It really depends on your table design. If you have no indexes or poor indexes, this will make performance incredibly slow - as will the design of your database in...
October 25, 2006 at 3:23 am
You can always copy them off and read them manually as they are just text files.
Look in the LOG folder of your SQL Server installation folder. It will be ERRORLOG...
October 25, 2006 at 2:35 am
What was the state of the indexes? Had the stats been updated recently? Was there any other process hogging resources - were other queries run at an acceptable speed?
October 25, 2006 at 2:27 am
It's really like guessing how long a piece of string is!
So many parameters to consider into settling on your own cpu threshold. Things like size of the database, tables being...
October 24, 2006 at 9:06 am
If you only want to add local roles or application roles and assign security, the db_securityadmin role would be a better bet.
In saying that, I'm not keen on anyone outside of the dba...
October 24, 2006 at 8:49 am
sleeping is either waiting for user input - for example, a query analyser session which is left open.
it can also be a spid waiting for a lock.
October 24, 2006 at 8:43 am
I see! Sorry, my mistake. I was refering to transaction log files!
Ed has described how to recycle your error log. It is normally restarted when the SQL Server service is...
October 24, 2006 at 8:12 am
Do you run regular transaction log backups? This is the easiest way. This will keep the logs a managable size.
My recommendation is to backup your transaction log. Once you have...
October 24, 2006 at 7:04 am
Good question. The average of 40% is not too much of an issue at all.
However, rather than a 1:40 perfomon trace, I would suggest setting up a perfmon counter trace...
October 24, 2006 at 6:56 am
I wouldn't say so it was corruption.
Did you check for any locks on the table?
Bouncing a server is a harsh way to resolve an access issue - this really is...
October 24, 2006 at 6:45 am
I agree with SQLBill.
Really not efficient. If your application requested 20 records with each call to the database, you'd end up with 200,000 calls to the database (400,000 in total...
October 24, 2006 at 4:02 am
Could be 2 things.
1) the spid is rolling back...From query analyser, run kill <spid> with rollback. This will give you a percentage of rollback completion.
2) the spid could have been...
October 24, 2006 at 3:43 am
Hi Yelena,
Thanks for the reply. No firewall between the servers.
It was a real odd one. I ran a sp_who on Server A, but there was no spids from Server B.
In...
October 24, 2006 at 3:39 am
Nice article. Been doing lots of digging around with data pages/indexes/heaps of late as it's a hot topic where I work. Looking forward to seeing the next article.
October 24, 2006 at 3:24 am
Hey,
Wow, thats a pretty immense question
As for configuring your server, the standard SQL configuration on installation will suit a lot of needs. ...
August 24, 2006 at 3:30 am
Viewing 15 posts - 361 through 375 (of 605 total)