RDA Push fails with SQL Server 2005 Compact Edition

Hello
I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
different schemas. I am in the process of developing a Windows Mobile 5.0
application that will work against this database, and Iâ'm planning to use
Remote Data Access with SQL Server 2005 CE to synch data.
I have my RDA all set up and working correctly IIS-wise, and have no problem
pulling a table from my database. However, when I attempt to push a modified
table back to the database, I get an â'Internal error: Failure setting up
bindings, possibly caused by insufficient permissions.â' error (which equates
to error 28621: SSCE_M_BINDINGS), which according to
http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
which â'cannot be resolved by common troubleshooting techniquesâ'. The
â'insufficient permissionsâ' is a red herring I think, since the problem
persists even if the SQL Server login that is being used for RDA is in the
sysadmin role.
Iâ've attempted to identify the problem by starting from scratch with a new
database and a new table with a couple of test columns. With the table
freshly created as dbo.TableName RDA works fine. However, when I create a
schema and transfer the table to the schema, RDA push fails as above, so to
me it looks like the schema is causing the problem.
Anyone any ideas about this? All help greatly appreciated!
Thanks - GrahamIn case this helps anyone else, I lodged a support call with Microsoft about
this and it has been confirmed that "SQL Server Compact Edition does not
support RDA.Push for non-default Schema tables". Hopefully this will be
fixed in the future.
"GrahamS" wrote:
> Hello
> I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
> different schemas. I am in the process of developing a Windows Mobile 5.0
> application that will work against this database, and Iâ'm planning to use
> Remote Data Access with SQL Server 2005 CE to synch data.
> I have my RDA all set up and working correctly IIS-wise, and have no problem
> pulling a table from my database. However, when I attempt to push a modified
> table back to the database, I get an â'Internal error: Failure setting up
> bindings, possibly caused by insufficient permissions.â' error (which equates
> to error 28621: SSCE_M_BINDINGS), which according to
> http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
> which â'cannot be resolved by common troubleshooting techniquesâ'. The
> â'insufficient permissionsâ' is a red herring I think, since the problem
> persists even if the SQL Server login that is being used for RDA is in the
> sysadmin role.
> Iâ've attempted to identify the problem by starting from scratch with a new
> database and a new table with a couple of test columns. With the table
> freshly created as dbo.TableName RDA works fine. However, when I create a
> schema and transfer the table to the schema, RDA push fails as above, so to
> me it looks like the schema is causing the problem.
> Anyone any ideas about this? All help greatly appreciated!
> Thanks - Graham|||There is a workaround for this problem - you can use a synonym in place of
the base table name. Crucially, the synonym must be named the same as the
base table ie 'CREATE SYNONYM dbo.MyTable FOR MySchema.MyTable'.
"GrahamS" wrote:
> In case this helps anyone else, I lodged a support call with Microsoft about
> this and it has been confirmed that "SQL Server Compact Edition does not
> support RDA.Push for non-default Schema tables". Hopefully this will be
> fixed in the future.
> "GrahamS" wrote:
> > Hello
> >
> > I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
> > different schemas. I am in the process of developing a Windows Mobile 5.0
> > application that will work against this database, and Iâ'm planning to use
> > Remote Data Access with SQL Server 2005 CE to synch data.
> >
> > I have my RDA all set up and working correctly IIS-wise, and have no problem
> > pulling a table from my database. However, when I attempt to push a modified
> > table back to the database, I get an â'Internal error: Failure setting up
> > bindings, possibly caused by insufficient permissions.â' error (which equates
> > to error 28621: SSCE_M_BINDINGS), which according to
> > http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
> > which â'cannot be resolved by common troubleshooting techniquesâ'. The
> > â'insufficient permissionsâ' is a red herring I think, since the problem
> > persists even if the SQL Server login that is being used for RDA is in the
> > sysadmin role.
> >
> > Iâ've attempted to identify the problem by starting from scratch with a new
> > database and a new table with a couple of test columns. With the table
> > freshly created as dbo.TableName RDA works fine. However, when I create a
> > schema and transfer the table to the schema, RDA push fails as above, so to
> > me it looks like the schema is causing the problem.
> >
> > Anyone any ideas about this? All help greatly appreciated!
> >
> > Thanks - Graham

RDA Push fails with SQL Server 2005 Compact Edition

Hello

I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
different schemas. I am in the process of developing a Windows Mobile 5.0
application that will work against this database, and I’m planning to use
Remote Data Access with SQL Server 2005 CE to synch data.

I have my RDA all set up and working correctly IIS-wise, and have no problem
pulling a table from my database. However, when I attempt to push a modified
table back to the database, I get an ‘Internal error: Failure setting up
bindings, possibly caused by insufficient permissions.’ error (which equates
to error 28621: SSCE_M_BINDINGS), which according to
http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
which “cannot be resolved by common troubleshooting techniques”. The
‘insufficient permissions’ is a red herring I think, since the problem
persists even if the SQL Server login that is being used for RDA is in the
sysadmin role.

I’ve attempted to identify the problem by starting from scratch with a new
database and a new table with a couple of test columns. With the table
freshly created as dbo.TableName RDA works fine. However, when I create a
schema and transfer the table to the schema, RDA push fails as above, so to
me it looks like the schema is causing the problem.

Anyone any ideas about this? All help greatly appreciated!

Thanks - Graham

In case this helps anyone else, I lodged a support call with Microsoft about
this and it has been confirmed that "SQL Server Compact Edition does not
support RDA.Push for non-default Schema tables". Hopefully this will be
fixed in the future.
|||There is a workaround for this problem - you can use a synonym in place of the base table name. Crucially, the synonym must be named the same as the base table ie 'CREATE SYNONYM dbo.MyTable FOR MySchema.MyTable'.

RDA Push fails with SQL Server 2005 Compact Edition

Hello

I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
different schemas. I am in the process of developing a Windows Mobile 5.0
application that will work against this database, and I’m planning to use
Remote Data Access with SQL Server 2005 CE to synch data.

I have my RDA all set up and working correctly IIS-wise, and have no problem
pulling a table from my database. However, when I attempt to push a modified
table back to the database, I get an ‘Internal error: Failure setting up
bindings, possibly caused by insufficient permissions.’ error (which equates
to error 28621: SSCE_M_BINDINGS), which according to
http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
which “cannot be resolved by common troubleshooting techniques”. The
‘insufficient permissions’ is a red herring I think, since the problem
persists even if the SQL Server login that is being used for RDA is in the
sysadmin role.

I’ve attempted to identify the problem by starting from scratch with a new
database and a new table with a couple of test columns. With the table
freshly created as dbo.TableName RDA works fine. However, when I create a
schema and transfer the table to the schema, RDA push fails as above, so to
me it looks like the schema is causing the problem.

Anyone any ideas about this? All help greatly appreciated!

Thanks - Graham

In case this helps anyone else, I lodged a support call with Microsoft about
this and it has been confirmed that "SQL Server Compact Edition does not
support RDA.Push for non-default Schema tables". Hopefully this will be
fixed in the future.
|||There is a workaround for this problem - you can use a synonym in place of the base table name. Crucially, the synonym must be named the same as the base table ie 'CREATE SYNONYM dbo.MyTable FOR MySchema.MyTable'.

Raw File as Source for Multiple Packages

I have a question regarding Raw Files. I am breaking a large package into more modular components for better processing and debugging.

The process will start with a preparatory dataflow that will create a Raw File(s). This Raw File will then be used as the source in possibly 6 data flows and/or packages.

My question is whether 1 Raw File can be read concurrently by the multiple jobs and how this would affect processing. I'm assuming that this would slow processing.

My other option is to Multicast the writing of the Raw File to 5 other versions of the file. All would be identical except for filename. Obviously this would use more disk space but this is not a concern as we have lots of disk space. Our concern is for speedy processing.

If you have experience with Raw Files, please let me know how you approached this issue. As always, blogs and specific examples are always great!

Thanks in advance.

Why not use a SQL Server table instead?|||

Do you mean to load my candidate items to a dynamically created temp table? And then I can query against this table in successive packages.

What is the process for creating the temp table? I think on my Control Flow palette, I use an ExecuteSQL task to execute a Create Temp table SQL...next a Data Flow Task can then load the table and finally after all Processing packages/flows complete, I use Execute SQL Task to Drop or Truncate the table.

Is this the process or is there a better way?

|||

omegarazor wrote:

Do you mean to load my candidate items to a dynamically created temp table? And then I can query against this table in successive packages.

What is the process for creating the temp table? I think on my Control Flow palette, I use an ExecuteSQL task to execute a Create Temp table SQL...next a Data Flow Task can then load the table and finally after all Processing packages/flows complete, I use Execute SQL Task to Drop or Truncate the table.

Is this the process or is there a better way?

This is the process, but I would like to add two refinements:

If you're going to be dynamically creating and dropping the table, be certain to build the first Execute SQL task so that it has a "IF EXISTS .. DROP TABLE; CREATE TABLE" logic, so it will run correctly regardless of whether the table already exists at run time. (Use the script generation tools in SSMS to build this script.) Set DelayValidation = True for any tasks that rely on the table, so the package can run regardless of whether the table exists.