Inherit From Executepackagetask
Jan 2, 2007
Hi,
is there a way to inherit from ExecutePackageTask? I try to build my own control flow component, mainly doing the same as the named task, with some special logging and configuration.
Application.LoadPackage(); Package.Execute(); Execute the Packages, but IMHO dont have the ability to jump into the package and show up the flow in the BI-Studio DebugMode.
So I will give it a try to inherit from ExecutePackageTask and customize the behavior.
Thanks
Thorsten
View 1 Replies
Jul 23, 2005
I have a database that looks something like this:Table: CreatureFields, CreatureId {PK}, ...Table: BugFields: BugId {PK}, CreatureId {FK}...Table: LadyBirdFields: LadyBirdId {PK}, BugId {FK}...Every creature in the system is in the Creature-table. If the creaturealso is a bug, then it's also in the bug table. And if it's aLadyBird, it's also in the LadyBird-table.A problem with the current design is that several bugs could be of thesame creature, and several LadyBirds could be of the same bug whichshould not be possible.So I'm thinking about removing the fields BugId and LadyBirdId, anduse CreatureId (as primary key) instead in the bug and ladybird table.Would that improve the design of the database? With a new design it'spossible to have a LadyBird that's not a Bug.I still thinks the new design would be better, but I'm gladly acceptadvices before I starts the redesign (which will be quite some work todo :-/ )PEK
View 2 Replies
View Related
Apr 10, 2008
I'm in the middle of developing some database independent code and I am surprised to find that the SqlCeException inherits from System.Exception not DbException. The argument I have seen is that DbException does not exist in the CE framework which I understand but this clearly breaks the model laid out by the other assemblies in the data namespace.
My issue is that I have a library which accepts an object implementing the IDBCommand. The execute command is wrapped in a try catch which is only interested in a DbException and allows all other exceptions through which therefore will allow and SqlCeException through.
I have three options available to me:
Catch all exceptions - This is not acceptable as other exceptions need to bubble up to the calling code.
Explicitly catch an SqlCeException - This too is not acceptable as it is a common library and not every application wants a reference to the SqlCe assembly
Explicitly catch an SqlCeException outside of the method call - As hideous as it is this is the only viable solution available to me meaning that any calling code using an SqlCeCommand must be aware of this "feature".
If anyone else has a suggestion I am willing to listen otherwise I'm going to go back to banging my head against the wall.</rant>
View 3 Replies
View Related
Jun 16, 2015
i have a little confusion...
DECLARE @name varchar(30)
SET @name = NULL
SELECT ISNULL(CONVERT(DATE,@name),'')
Result: 1900-01-01
But..
DECLARE @name varchar(30)
SET @name = NULL
SELECT ISNULL(@name,'')
Does NULL inherit a datatype after convert?
View 7 Replies
View Related
Feb 1, 2008
Hey there,
Trying to build a temporary table based on a parent table such that:select * into #staging from tbl_parent where 1=0
The temp table (#staging) picks up any NOT NULL constraints from the parent (tbl_parent) table and frankly, it doesn't meet my needs.I also tried to build a view of the parent (tbl_parent) table from which to base my SELECT INTO and still, the constraints followed.
I'm thinking perhaps it possble to iterate though the temp table using syscolumns sysobjects and and set the column NULL properties on the temp table AFTER its been created but in this approach, I'm working to avoid directly referencing the columns by name.
Is this possible? A better answer perhaps?
Purpose of exercie is to populate a record in memory before it hits the table.I'll be constructing the record on the fly so that at first, I won't have all the fields to de-Null the columns.Also, I don't wish to lose the fact that some of my fields are Null - once I've fully populated my temp record, I'll insert into my 'real' table and will depend on constraints to throw the appropriate error. In this I won't have to built custom error checking in the stored procedure itself but instead depend on SQL SERVERS built capacity to the throw the error. This opens a bunch of possibilities for extensibility since if at a later date a constraint rule changes, one need only change the parent table definition rather than cracking open the stored procedure.
Thank you for reading and a big thanks to you for replying :)
Also,
View 11 Replies
View Related
May 23, 2007
As you all know, in Framework 2.0 on the desktop platform you have the convenient "abstract" Db* classes that can be used to write more generic code. For instance System.Data.SqlClient.SqlConnection inherits from System.Data.Common.DbConnection, and so forth. Now the docs clearly say that this applies to the corresponding classes in the Compact Framework. And i have seen this implied by other web searchs I've done. However this does not seem to be the case -- or, I'm missing something somewhere.
The following simple code on the desktop platform compiles OK:
using System.Data;
using System.Data.Common;
using System.Data.SqlClient;
DbConnection conn = new SqlConnection();
However it doesn't compile in a compact framework project: "Cannot implicitly convert type 'System.Data.SqlClient.SqlConnection' to 'System.Data.Common.DbConnection'".
Reflector also indicates that the Compact Framework class doesn't inherit from DbConnection.
OK, so am I missing something here, or what was the reason that Microsoft did it differently??
View 1 Replies
View Related
