Advanced reporting
and data visualization components for .NET
LIVE CHAT Welcome, guest

 





Feature request/Solution to a problem for SQL Scnema Sync API
Display Posts for:
Invert
Robert Rupf 05/20/2010 12:45
Feature request/Solution to a problem for SQL Scnema Sync API

Hello there,

after evaluating your great component we encountered a critical problem, which prevents us to use the SQL Scnema Sync API.

The following errors occured on MSSQL Server 2005 with Windows Server 2003 SP2.

Comparing of two databases was successful, but the generated update-script tries to create a view on a table, which is constructed just before it.
MSSQL-Server rejects the script with following error message: "CREATE VIEW must be the first statement in a query batch."

To avoid the problem a simple "GO" to signal the end of such an batch would solve this point of failure.
The same solution would be nescessary for stored procedures.

As far as i know "GO" just executes the batch so far received. Therefore it would not be harmful to use it after such critical queries.

Another problem occured during a REVOKE/GRANT-command: The specified principal has a white-space in its name. Because of that an error is raised. If we manually parenthesise this name, the error disappears.

If these simple features can be realised, we would be more than happy to use SQL Scnema Sync API.

I must admit I had not much time to scan the SQL Schema Sync API Class reference. Maybe the solution can be triggered by simply calling a method.

I am sure you have a much greater knowledge about MSSQL Server. Therefore I am looking forward to an answer from you in the hope you can present a nice solution for our problems.

Bye,
Xong
Robert Rupf 05/20/2010 12:57
Feature request/Solution to a problem for SQL Scnema Sync API

Hello,

in order to clarify the problems I give you some examples.

VIEW-problem
Failed batch
Code:
CREATE TABLE t1 ( ... )
CREATE VIEW v1 AS ...

Solution
Code:
CREATE TABLE t1 ( ... )
GO
CREATE VIEW v1 AS ...


GRANT/REVOKE-problem
Failed batch
Code:
REVOKE SELECT TO name with white-space

Solution
Code:
REVOKE SELECT TO [name with white-space]


I hope this is going to help you understanding me a little bit better. :-)

Thanks,
Xong
Vlad Nekrasov 05/21/2010 06:04
Feature request/Solution to a problem for SQL Scnema Sync API

Hello,

Thanks for your notice, we will think over the solution of this problem

Best regards,
Vlad Nekrasov
Perpetuum Software Team
Robert Rupf 05/21/2010 09:19
Feature request/Solution to a problem for SQL Scnema Sync API

Quote:
Thanks for your notice, we will think over the solution of this problem

Thank you.

We are looking forward to it.

Greetings,
Xong
Vlad Nekrasov 05/25/2010 07:01
Feature request/Solution to a problem for SQL Scnema Sync API

Hello,

We will answer you as soon as we will find a solution.
Thanks for your patience.

Best regards,
Vlad Nekrasov
Perpetuum Software Team
Vlad Nekrasov 05/25/2010 07:01
Feature request/Solution to a problem for SQL Scnema Sync API

Hello,

We will answer you as soon as we will find a solution.
Thanks for your patience.

Best regards,
Vlad Nekrasov
Perpetuum Software Team
Robert Rupf 06/15/2010 06:43
Feature request/Solution to a problem for SQL Schema Sync API

Hello!

Though still evaluating the SQL Schema Sync API, I found a way around this problem with Search & Replace.
Problem is, we now can not use the Update-Method of the API, but we have to send the Batches on our own.

So we would be more than happy, if u can fix this bug asap.
I suppose it isn´t much work, because there are only some brackets missing. :P

Best regards,
Xong
Robert Rupf 06/15/2010 06:47
Feature request/Solution to a problem for SQL Schema Sync API

Hello again!

By the way, why is it not possible to change a batch with the help of the ScriptExecuting-Event?

That would be more than helpful in this case.

Best regards,
Xong
Vlad Nekrasov 06/17/2010 06:27
Feature request/Solution to a problem for SQL Schema Sync API

Hello,

Thank you for your remarks. We are exemining our product functionality at the moment and unfortunately I can't specify any terms for this issue.

Best regards,
Vlad Nekrasov
Perpetuum Software Team