I am writing a basic file dump from one database to another. I am using SSIS 2008 and creating several packages to transform the data I have from a MSSQL 2010 database to a MYSQL 5.1 database.
I realize that temporary tables are session/connection bound and not visible or accessible out of the session/connection.
Can anyone break it down in plain English the performance difference between using temp tables vs. CTE\'s vs. table variables in MSSQL. I have used temporary tables quite frequently and have started u
UPDATE: I\'ve included complete code that can be pasted into SSRS, to show the results. We report on lots of date-centric information and have to produce reports from it. Some of the source data isn\
Our client\'s database admins have requested that we don\'t use temp tables within our reporting stored procedures (#Table), but instead, make use of table variables.
I pondered on this one a little bit. Found a few question on SO but none of them addressed my problem.
OK, so I do suck at MySQL, but here is basically what I want to do: delete from course_plan_relationships
Given the example queries below (Simplified examples only) DECLARE @DT int; SET @DT=20110717; -- yes this is an INT
I can think of two main benefits: Avoiding concurrency problems, if you have many processes creating/dropping tables you can get in trouble as one process tries to create an already existing table.
here my query- SELECT final.* into #FinalTemp from ( select * from #temp1 UNION select * from #temp2 UNION