Our server has 4 processors. Long running queries will use all of them until they finish, effectively preventing other users from retrieving data during that time. Is there any way to configure SQL Server 2000 to restrict processor usage?
I have read that "every table should have at least one unique clustered index". I have also been told that if a column is a member of a comopsite index, queries that group or have 'where' clause on that column will not perform as well as if that column were indexed independently. So...
I run a monthly DTS job that loads the contents of a text file into a temp table, then an insert query does some simple manipulation of the data and passes it to a cumulative table. Each of the tables resides in a different filegroup on a different drive share.
During my last update, the insert...
We currently run a weekly full backup and daily differential backups using Veritas. The problem we are having is that the transaction log will only truncate following a full backup. We are going through a rapid growth phase where the log grows by as much as 50GB per day. Disk space on our server...
Thanks for you help. It seems that the only way to do it is the individual save as, changing the server designation. We had about 50 DTS to move, so I was hoping to do it with one copy.
I was running a long query (in SQL Query Analyzer) today and after about 40 minutes, a temp file (qag7a.tmp) appeared on my pc. It seemed as though SQL server was using my local processor (processor was at 100% in the task manager). The temp file quickly used up all available disk space and did...
Thanks, Terry. I agree completely. The queries are just selects, but not all of the joined fields are indexed. I'm sure that has a significant impact. Considering that the purpose of the queries is to validate data in a new table (they won't likely be used again), I didn't want to invest the...
That's what I asked.
There are some long running queries that are using all of the available disk space (yeilding an error: log file for temdb is full). I wanted to point temmplog.ldf to a larger disk (it only has 5GB available on the current disk), but our dba insists that it would be better...
If I have tables joined on two columns in each table, what is the advantage of using a compostite index as opposed to indexing each column individually?
Table 1 (1.3 million rows): Primary key is comprised of three colums (customer, date, item) and I have set this up as a clustered index. There is also a salesperson field that is not indexed (yet).
Table 2 (50,000 rows): Primary key is comprised of two columns (salesperson, customer). These...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.