Just like you would have to if creating a permanent table. Base the column types off the data you are going to load from your queries.

To be safe, I'd disable the job while deploying a fully tested update to the SSIS package.

At the start of your stored procedure, create your temporary table. Then use INSERT to put the records into the temp table. Do your additional processing.

I'd set the autogrowth to a fixed amount, not a percentage.

debbie.coates (10/29/2008)

---

(This isn't my actual select query, its just an example, but i still get the same error aobut there alread being a #temp. Is it something to do...

How about posting the actual queries you are running?

Davroche (10/29/2008)

---

We need the DDL for the table(s), create statements. The tables are already there I did not create them. I am simply querying the data. I...

Read the article identified below, then post the DDL for the table, some sample data, and the expected results based on the sample data. This will help us help...

That would work also.

Use your DDL trigger to dynamically build and start a job that performs the backup operation. The job should also delete itself upon successful completion so that you don't...

Easy fix:

select

a.cuslink,

a.sequence,

a.effdate,

a.site,

a.entercd

from

#list1 a

...

Glad it worked. I'm not that familiar with SQL Server 2005 Compact Edition, so wasn't too sure what I could and couldn't do.

Here is some code without a loop:

with SixValues (

num

) as (

select 1 union

select 2 union

select 3 union

select 4 union

select 5 union

select 6

)

select

datename(mm,dateadd(mm,datediff(mm,...

rbarryyoung (10/28/2008)

---

Depends on what you mean by "quick":

Insert into ptApointment(...)

Select ...

From ptSchedule s

Where ScheduleID NOT IN(Select Cast(a.ID as int) from ptApointment a

...

Mike (10/28/2008)

---

I'm writing a query that is allowing the user from my web page to do a search with selecting parameters and a date parameter is one of them...