Viewing 15 posts - 21,031 through 21,045 (of 59,098 total)
richardmgreen1 (4/16/2015)
I did think of that, but it doesn't seem to persist.
This what I had 10 minutes ago:-
USE SystmOneData
EXEC sys.sp_MSforeachtable '
truncate table ?
begin try
set identity_insert ? on
end try
begin catch
end...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 7:11 pm
mxy (4/16/2015)
insert into LSDestserver.DB.dbo.tablename
select * from #temp order by abc desc
I initially thought...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 7:05 pm
Ummm.... are you sure that's ANSI Pig Latin??? 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 5:57 pm
sql-lover (4/16/2015)
Zeal-DBA (4/14/2015)
my update query updating approx 50 million record which is causing transaction log to grow, and filling disk space and finally transaction is failing, please suggestany worl around.
My...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 5:55 pm
kk.86manu (4/16/2015)
Hi All,Is it always the best practice to have the partition column also as the column for clustered index?
No. It seriously depends. If the clustered index is...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 5:52 pm
Very cool. Thanks for posting what you found out. Not too many folks do that. I, for one, appreciate it.:-)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 5:47 pm
marc.heidemann (4/16/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 5:17 pm
sKreetz! (4/16/2015)
Thanks again guys for the responses, and thank you lyncc! Does anybody know where I can find a complete list of sql functions with descriptions to study?
Yes. Sql...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 5:06 pm
SQL-DBA-01 (4/16/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 4:57 pm
As to your problem, you're taking the value of @@Rowcount before the EXEC for each command.
You've also made things a bit complicated. The following (for example)...
SET @rows_affected1 = (SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 4:53 pm
In a totally unrelated area, why are you using dynamic SQL for every command? It's not needed.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 4:47 pm
DataAnalyst011 (4/16/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 4:34 pm
Alan.B (4/16/2015)
If that's not an option, and if Lowell's solution (enable xp_cmdshell then disable when you're done)...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 4:23 pm
Gary Harding (4/15/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 4:11 pm
GF (4/16/2015)
Thank you for the reply.xp_cmdshell is disabled and our policy is to keep it disabled.
For SSIS I have no experience with SSIS.
Too bad. It's an incredibly useful tool...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2015 at 3:49 pm
Viewing 15 posts - 21,031 through 21,045 (of 59,098 total)