This here is for everyone who has ever needed to shrink that transaction log and couldn't. This script shrank a 3 gig transaction log to 600 MB in about a minute and a half.
Supposedly this was found on MSDN, but I have never been able to find much of any value on MSDN without bleeding from my...
Thanks folks.
We did get this to finish, I was just trying to optimize this so that it would not take an hour to complete. I will tweak the recovery interval, as suggested by foxdev, but I believe the SET ROWCOUNT option is not a valid solution, because processing stops upon reaching the...
That is probably the answer. Just a follow up question. So if I use the SET ROWCOUNT = 1000000 statement, will my process stop after the first million, or will it continue in increments of a million?
I understand that this might have to be programmatically induced.
Thanks for steering me...
We are performing a migration from BTrieve to SQL 7. Last night while inserting the results of a two table join that resulted in a table of 14.6 million records, we found that increasing the size of the tempdb, while allowing automatic growth of the log file, with "Truncate on...
From SQL Server BOL
Sorry about formatting, Right Hand Column is SQLS 7
Maximum Capacity Specifications
This table specifies the maximum sizes and numbers of various objects defined in Microsoft® SQL Server™ databases, or referenced in Transact-SQL statements.
Maximum sizes/numbers
Object...
I found this in BOOKS ONLINE:
CHECKPOINT (T-SQL)
Forces all dirty pages for the current database to be written to disk. Dirty pages are data or log pages that have been modified after they were read into the buffer cache, but the modifications have not yet been written to disk. If the current...
I have had luck with the following bit of VB code when I am accepting values from an ASP page:
If Not IsNull(vntData(0)) Then
vntData(0) = Replace(vntData(0), "'", "`", 1, -1, _ vbTextCompare)
End If
If you threw all that stuff into a staging table first and then cleaned...
You should be able to do this by taking in the column as a varchar(xx). Once the parameter is inside the stored procedure, use the LEN function to determine the length of the parameter, and then parse through the parameter using a for loop to obtain the values for col3 in the expression ...
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.