Viewing 15 posts - 466 through 480 (of 497 total)
I know this is somewhat 'shutting the stable door after the horse has bolted', but it may help prevent such a drastic problem another time if you limit the size...
May 26, 2009 at 11:04 am
True, but permissions to tables should be under exclusive control of DBAs whereas ACL could be changed by IT Ops/Domain Admins etc.
May 18, 2009 at 10:15 am
zanoni.harris (5/14/2009)
...what I mean is what the advantages...
May 18, 2009 at 8:08 am
BCC
I can think of a couple of ways off the top of my head, but there are probably others.
1. Using variables and expressions.
2. Using a script task(!)
The choice...
May 11, 2009 at 3:16 am
Paul Paiva (5/7/2009)
As was clearly stated in the "Purpose/Scope" section of the article, the intention is to show how you can use a script task to send email....
May 8, 2009 at 7:03 am
BCC,
Hopefully these screenshots shold give you a start.
You'll need to add expressions to the Send Mail task which will reference existing variables.
You can test your expressions for syntax errors...
May 8, 2009 at 4:35 am
Ken (5/6/2009)
....unless you have very long running scrips AND (not OR) concurrent process that use them.....
Precisely. If you want to design your packages to be able to take advantages of...
May 7, 2009 at 7:51 am
If you are going to use a Script Task (and I wouldn't personally for reasons already stated in previous posts), you should use the concepts LockForWrite/Read and LockOneForWrite/Read rather than...
May 6, 2009 at 11:09 am
Brett Flippin (5/6/2009)
May 6, 2009 at 9:06 am
Useful article, but I think it is easier to use the Send Mail task with Expressions to dynamically set properties such as MessageSource, To, From, Subject etc.
May 6, 2009 at 6:19 am
Automatic Page Repair is available in Enterprise and Developer Editions for SQL Server 2008, so as 'Developer Edition' was not listed in the available answers I guess that 'Enterprise only'...
April 8, 2009 at 2:23 pm
Running SQL Server under the Local System account is dangerous as the account has far more privileges than it needs. Try to avoid this if at all possible and check...
April 8, 2009 at 2:12 pm
Laura,
To set up a SQL Server Log Provider, do the following steps:
[font="System"]1. Open the package for which you want to configure logging in BIDS.
2. Select 'Logging...' from the SSIS menu.
3....
April 8, 2009 at 7:16 am
Jack,
There is no direct correlation between the Log Providers and failing packages/data flows, By that I mean that the use of a Log Provider in and of itself will not...
April 6, 2009 at 4:04 am
Jack,
The solution clearly provides what you want in terms of error handling/logging, but wouldn't it be easier to use the Log Providers that are readily available with SSIS? For example,...
April 4, 2009 at 10:28 am
Viewing 15 posts - 466 through 480 (of 497 total)