Viewing 15 posts - 31 through 45 (of 261 total)
jsheldon (5/23/2008)
Let me ask this, within my excel source data task can I add an identity column? That would be much easier than this script task.
If your configured properly...
May 23, 2008 at 12:23 pm
To answer your question, why not make an identity column on the destination table. That would make life too easy 😉
The data is a telephone activity going into a...
May 23, 2008 at 11:55 am
Trying to compare each value in every record to that currently in the table is agonizing for the cpu and extremely low performing. Instead try to identify something in the...
May 23, 2008 at 11:26 am
You might want to look at storing those username/password combos in an encrypted manner inside SQL to better protect the data. Of course you would need to include a script...
May 23, 2008 at 10:19 am
If your package is inserting the data into a staging area why not just add an identity column to the staging table for row number? You might also just insert...
May 23, 2008 at 10:14 am
What is the condition on which you want to split the column? You may use a derived column yes...
Go here: http://msdn.microsoft.com/en-us/library/ms141232.aspx for some details on the expression language...
May 22, 2008 at 3:27 pm
Like so:
SELECT
CONVERT(CHAR(10), Title)
+CONVERT(CHAR(75), FirstName)
+CONVERT(CHAR(75), LastName)
+CONVERT(CHAR(100), EmailAddress)
FROM
AdventureWorks.Person.Contact
May 22, 2008 at 11:24 am
What I've done in the past to accomplish this is to concatenate all my fields in my select list together while converting to char values with hardcoded lengths. This way...
May 22, 2008 at 10:44 am
Use the same 'Execute SQL Task' I suggested for the Master package and add a condition to your precedence constraint that specifies @Exists =1 for example...
May 21, 2008 at 3:35 pm
Might it make more sense to not hardcode the RecType in there?
May 21, 2008 at 3:16 pm
Can you provide some additional details about exactly what you are trying to accomplish?
May 21, 2008 at 11:12 am
Underdog,
Have these packages been deployed to a production or are you just running them locally? Just a hunch but that may be why you're seeing such shotty performance...
Also, you said...
May 21, 2008 at 11:10 am
To thenepatsrule: You would never want to deploy a package to production that required user interaction such as a message box.
To Bindu: xp_cmdshell is dangerous which is why it is...
May 21, 2008 at 10:50 am
xp_cmdshell is disabled by default in SQL 2005 so unless you have had your administrators enable it (not recommended) you won't be able to use it. Like Lynn said, us...
May 21, 2008 at 10:33 am
If you are familiar with SSRS...
http://technet.microsoft.com/en-us/library/ms156012.aspx
If you are not, first get acquainted and build the simple report, then use the above link to create the data-driven subscription...
May 21, 2008 at 10:31 am
Viewing 15 posts - 31 through 45 (of 261 total)