Viewing 15 posts - 61 through 75 (of 79 total)
Oh! I couldn't believe as I thought that the condition "@@rowcount > 0" will take care of it.. however I will try using a condition..
Thank you all for your contribution...
December 3, 2013 at 7:22 am
thanks for your interest...
Please check the below code..
set rowcount 40000
Update T1 SET sName = t2.sName
from dbo.t_table1 T1 INNER JOIN dbo.t_table2 T2 ON t1.tID = t2.tID
while @@rowcount>0
begin...
December 3, 2013 at 7:06 am
May be.. but I didn't use begin transaction to use commit.. should I include begin tran... end tran with commit..?
Else that query will continue running indefinitely? :w00t:
December 3, 2013 at 6:41 am
Hope I can continue on this thread.. since its regarding the same issue..
SQL Server in one of our VM machine is giving timeout expired while logging in through SSMS on...
October 29, 2013 at 11:44 pm
Actually I found an old thread regarding the same issue.. so I thought of opening a new one
July 5, 2013 at 5:58 am
Most of our queries use lot and lots of temp tables, however the tempdb size will not exceed 2GB. When I try to rebuild index, it takes more than 2...
May 16, 2013 at 5:30 am
Sure, I will try to do that. However, how will you conclude on the requirement if reads are more. The performance counter shows 99.8%-100% for SQL Buffer Manager in all...
May 16, 2013 at 2:57 am
Thanks for your suggestion, anyways I am responsible to recommend so and so hardware requirements. But our server consultant is not providing sufficient resources that I demand.
So, could you...
May 15, 2013 at 2:43 am
you can just use DBCC shrinkfile or DBCC shrinkdatabase command without truncate_only.
visit this site for details.
May 15, 2013 at 12:09 am
please avoid restarting the SQL Server. Use the below query to shrink tempdb after stopping the queries responsible for its growth.
use tempdb
go
DBCC SHRINKFILE(templog, 80)
GO
BACKUP LOG tempdb WITH TRUNCATE_ONLY
GO
DBCC SHRINKFILE(templog, 80)
GO
80...
May 14, 2013 at 11:23 pm
I have the same thought as you do. But if the tempdb is too full, find the queries or SPs responsible for the tempdb growth and stop them before shrinking...
May 14, 2013 at 11:14 pm
Hi Stefan,
I am using the below command just to monitor currently running scheduled job since the output will reflect very late in another table.
EXEC msdb.dbo.sp_help_job @execution_status = 1
April 25, 2013 at 12:47 am
Alternatively, we can use this too.. it takes about an hour to delete a million records
set rowcount 50000
DELETE FROM EventTracking.dbo.Event
while @@rowcount>0
begin
set rowcount 50000
DELETE FROM EventTracking.dbo.Event
END
set rowcount...
March 6, 2013 at 3:42 am
Hi SSCrazy -
In that case, please explain about the filegroup restoration chain..:-)
February 6, 2013 at 5:38 am
Viewing 15 posts - 61 through 75 (of 79 total)
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy