Catadmin,
I am running the maintenance plan for my database once a week on Sunday already. I have it set to optimize data pages and indexes, amongst others.
I am finding that some (huge) insert statements are running slowly after the weekend, so my guess was it is because I also shrink the...
addendum:
A dirty way to check if the property is set is by examining the
DTS.Connection2.UseDSL
DTS.Connection2.UDLPath
properties.
If the property is set to FALSE:
UseDSL = -1
UDLPath = ""
if TRUE:
UseDSL = -1
UDLPath = <a path here>
This is because if the property is not set the...
I cannot find a certain property in the DTS object model:
"always read properties from UDL file" which can be found on the property tab of a UDL connection in a DTS package.
My guess is it would be in one of the following objects:
DTS.Connection2
DTS.OleDBProperty2
But I cannot pinpoint...
thanks mrdenny,
some questions i still have:
1) does your argument also hold for shrinking the transaction log? the shrinkdatabase statement shrinks both, but the transactions in the transaction log (LDF) are commited to the database file and the file is "emptied" (perhaps some open...
Hello,
I have a database with a transaction log file of 500MB. I want to increase it to 10000MB, but this must also become the new "minimum logsize".
According to BOL the ALTER DATABASE statement with the SIZE=10000MB property should do the trick... BUT after an autoshrink or forced shrink (...
Hi,
A dts package can log errors per step to the sysdtssteplog table. An error description can be found in the errordescription field.
HOWEVER, this message is maximum 256 characters long, while the datatype is nvarchar(2000). Some descriptions are truncated, while I need the entire message...
Why is it not possible to KILL a SELECT process? The BOL states this is one of several process that can't be killed.
If users are retrieving vast amounts of data, taking up to many resources, those processes can't be killed?
What's the risk? That users receive partial result sets?
Has...
You could catch the result in a variable and using output variable(s) in your procedure:
declare @cmd nvarchar(4000)
declare @arg2 blabla
exec some_proc @arg1, @arg2 out
@cmd = 'Update some_table set some_col=' + @arg2
(If @arg2 is not numeric, put it in quotes)
finally:
exec sp_executesql @cmd
Set objRS.CommandTimeout to a higher value than the default 30 seconds, e.g. 1000
objRS.CommandTimeout = 1000
It looks like it is not a connection (i.e. slow reverse lookup of the server name) problem. BUT if the previous statement doesn't fix your problem, try the next one...
I guess your code is a sort of pseudo-ASP code: constructing an SQL statement via APS code, but you removed the annoying <% and %> tags :)
I don't completely understand your question, but my guess is you have to change:
theSQL = theSQL & ") AND eat IN ('BOTH')"
to
theSQL = theSQL &...
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.