As an aside, if you need help with SQL 2005 it's best to post in the SQL 2005 Forums otherwise you may get 2008-specific responses.

For you particular issue, and this...

Not ideal but I can work with that for DDL...can you please provide some test data?

Please have a look a this article: http://www.sqlservercentral.com/articles/Best+Practices/61537/%5B/url%5D

I would like to help...kindly post the DDL for your tables and DML to generate some useful test data.

Please post DDL and some DML to create test data for your tables:

asap_email_listTrain

TRAIN..SALES.DEL

TRAIN..MISC.ZIP2ZONE

http://www.sqlservercentral.com/articles/Best+Practices/61537/%5B/url%5D

It will depend on the output of the sig pad so the answer will be specific to the hardware and software provided by the vendor...I suggest you work with them.

One...

Mapping a Data Reader Source to an OLE DB Destination will give you the option to create the table in the destination...however other than column names and data types nothing...

Did you look at the Event Log? Please post the details of your findings so we may help you arrive at a solution.

It looks like it has been fixed.

Lionel E. Nzenze (3/11/2011)

---

Bad Idea..

So not send mail from a trigger.

Get the Trigger to write Whatever you want into some table.

Create a SQL Server Job to poll the said table...

Try this:

SELECT ...,

REPLACE(CONVERT(CHAR(10), CONVERT(DATETIME, [column_name]), 101), '/', '-') + ' ' + CONVERT(CHAR(12), CONVERT(DATETIME, [column_name]), 114) AS my_new_date,

...

FROM [some_table];

Edit: missed the replace, thanks bitbucket

You can do this with sc.exe:

http://technet.microsoft.com/en-us/library/bb490995.aspx

nico van niekerk (7/15/2008)

---

It IS important in which order columns are specified in a table. Having varchar columns preceding fixed-length columns place an undue burden on the server because of...

It can be done using a couple Windows Batch commands to accept the user's input into StdIn and by calling sqlcmd.exe to execute the SQL. I woudl recommend putting your...

Redesign your data model 🙂

Just kidding (not really)...boolean in SQL Server is implemented as the BIT data type where 0 = false. As an aside, NULLable bits are allowed too...

Anything with a Severity <= 10 will be treated as "informational" and will not affect batch execution (i.e. will not set @@error). It will however cause data to be sent...