Viewing 14 posts - 16 through 29 (of 29 total)
odbc is probably timing out.
how long does the query take?
increase odbc timeout to larger value or consider revising query so it is faster.
July 13, 2006 at 10:49 am
did you upgrade the server or move the DBs to a new server?
does that table exist?
who is owner?
are server logins and db users in synch?
June 23, 2006 at 3:34 pm
consider multiple segments for data (mdfs).
then you could partition tables or seperate indexes from table data
June 22, 2006 at 3:00 pm
killing restore will probably put db in bad state.
to stop the restore you should be able to kill the process running the restore or stop the sql service or restart...
June 21, 2006 at 11:15 am
indexes should speed things up.
on the main table with ID, make the index clustered
and unique if possible
on the temp table
create index ix_tmpid on ##TMP(id)
join should be faster then the IN...
June 21, 2006 at 11:00 am
just use the sps -
sp_help_job
sp_help_jobhistory
...
sp_help_maintenance_plan
...
June 21, 2006 at 10:49 am
if only difference is
and UBNR = '001'
I would guess it is table scanning UBNR
add an index on that column (and all others in the "where" clause)
May 12, 2006 at 12:52 pm
are deadlocks during inserts?
perhaps lower fill factor.
if clustered pk has to move a lot of pages to insert new rows it may take a while.
sometimes good not to have the...
May 12, 2006 at 12:49 pm
what is the dbcc, maybe write an sp that duplicates the dbcc function?
May 10, 2006 at 11:02 am
it is fairly simple -
old server:
export logins or copy via dts
backup dbs (use a script) or detach and move files
script jobs
script replication
note linked servers (not aware of a script...
May 4, 2006 at 11:14 am
either add transaction log backups to the maintenance plan or change the db to simple.
if log has grown, probably shrink it after the data used decreases.
May 4, 2006 at 11:02 am
have you tried increasing the size of tempdb to see what happens?
maybe up to 200 or 500 mb if you have drive space.
also the tables that the queries run against...
May 3, 2006 at 10:44 am
dynamic sql is not good for a number of reasons. stay away from it if you can. sounds like the dynamic sql is different then the working non-dynamic...
May 3, 2006 at 10:37 am
I was having problem.
was able to fix by exec xp_stopmail
and then xp_sendmail
do not xp_startmail before xp_sendmail
March 10, 2006 at 11:24 am
Viewing 14 posts - 16 through 29 (of 29 total)