Showing posts with label environment. Show all posts
Showing posts with label environment. Show all posts

Friday, March 30, 2012

Read80Trace.exe in SQL Server 2005

My present production environment is in SQL Server 2000 and we are
planning to upgrade to SQL Server 2005 soon. I use the profiler a lot
and then use Read80trace.exe to process the trace files.
However, the Read80Teace does not accept a trace file from SQL Server
2005 and a SQL Server 2000 profiler does not connect to SQL Server
2005.
Are there any other tools similar to Read80Trace.exe for SQL Server
2005? If not, is there a way to trick the tool to accept a file from
SQL server 2005?
Thanks.
Sorry that I can't answer your question but I was hoping to get some help from you. I am interested in using Read80Trace.exe but have some questions on it. What specific eventclasses do you use when capturing your profile for use with Read80Trace? t
he documentation talks about capturing different events for different needs but is unclear as to what exactly is needed for use as a "minimul set". I would like to use the capture for reporting but do not need all of the events because I am not going to
use the Ostress tool. I just want the minimul set of events to get the most out of reporting... Any help you could offer would be greatly appreciated...
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
|||Hi
The format of trace files seems to be different to SQL 2000, but you can
work around this by loading the SQL 2005 trace into a table and then
exporting it back into SQL 2000. You can then use SQL 2000 profile to read
the table and save it as a trace file to feed into Read80Trace.
John
"baddy" wrote:

> My present production environment is in SQL Server 2000 and we are
> planning to upgrade to SQL Server 2005 soon. I use the profiler a lot
> and then use Read80trace.exe to process the trace files.
> However, the Read80Teace does not accept a trace file from SQL Server
> 2005 and a SQL Server 2000 profiler does not connect to SQL Server
> 2005.
> Are there any other tools similar to Read80Trace.exe for SQL Server
> 2005? If not, is there a way to trick the tool to accept a file from
> SQL server 2005?
> Thanks.
>
|||Hi
The event classes for Read80Trace are listed in the help file as
·SQL: Cursor Open/Close – Cursors
·Attention - Errors and warnings
·Audit:Login/Logout - Security Audit
·ExistingConnection - Sessions
·RPC:Starting/Completed - Stored Procedures
·RPC:OutputParameter - Stored Procedures
·Prepare/Unprepare SQL - TSQL
·SQL:BatchStarting/Completed – TSQL
If you use the scripted trace in the help file then it seems to log
everything, therefore if you want to script the trace I would create your own
by setting up the events above and using the file/script trace option in SQL
Profiler. These are the events for capture
For aggregation analysis check out the events described in the Events &
Columns for Aggregation in the Design Overview. This lists
·Audit:Login/Logout - Security Audit
·ExistingConnection - Sessions
·RPC:Starting/Completed - Stored Procedures
·SP:Starting/Completed - Stored Procedures
It does not list the following, but if you are not using stored procedures
you may want to also capture (I have not seen if these are used in the
analysis)
·SQL:BatchStarting/BatchCompleted – TSQL
·SQL:StmtStarting/StmtCompleted – TSQL
John
"Paul S" wrote:

> Sorry that I can't answer your question but I was hoping to get some help from you. I am interested in using Read80Trace.exe but have some questions on it. What specific eventclasses do you use when capturing your profile for use with Read80Trace?
the documentation talks about capturing different events for different needs but is unclear as to what exactly is needed for use as a "minimul set". I would like to use the capture for reporting but do not need all of the events because I am not going t
o use the Ostress tool. I just want the minimul set of events to get the most out of reporting... Any help you could offer would be greatly appreciated...
> ************************************************** ********************
> Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
> Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
>
|||Something else...
I had issues with transfering the columns of image datatype, so don't
capture BinaryData and LoginSID.
John
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> The event classes for Read80Trace are listed in the help file as
> ·SQL: Cursor Open/Close – Cursors
> ·Attention - Errors and warnings
> ·Audit:Login/Logout - Security Audit
> ·ExistingConnection - Sessions
> ·RPC:Starting/Completed - Stored Procedures
> ·RPC:OutputParameter - Stored Procedures
> ·Prepare/Unprepare SQL - TSQL
> ·SQL:BatchStarting/Completed – TSQL
> If you use the scripted trace in the help file then it seems to log
> everything, therefore if you want to script the trace I would create your own
> by setting up the events above and using the file/script trace option in SQL
> Profiler. These are the events for capture
> For aggregation analysis check out the events described in the Events &
> Columns for Aggregation in the Design Overview. This lists
> ·Audit:Login/Logout - Security Audit
> ·ExistingConnection - Sessions
> ·RPC:Starting/Completed - Stored Procedures
> ·SP:Starting/Completed - Stored Procedures
> It does not list the following, but if you are not using stored procedures
> you may want to also capture (I have not seen if these are used in the
> analysis)
> ·SQL:BatchStarting/BatchCompleted – TSQL
> ·SQL:StmtStarting/StmtCompleted – TSQL
> John
> "Paul S" wrote:
? the documentation talks about capturing different events for different needs but is unclear as to what exactly is needed for use as a "minimul set". I would like to use the capture for reporting but do not need all of the events because I am not going
to use the Ostress tool. I just want the minimul set of events to get the most out of reporting... Any help you could offer would be greatly appreciated...[vbcol=seagreen]
|||Opps.. this was supposed to be on my reply to baddy's post!!!
"John Bell" wrote:
[vbcol=seagreen]
> Something else...
> I had issues with transfering the columns of image datatype, so don't
> capture BinaryData and LoginSID.
> John
> "John Bell" wrote:
ce? the documentation talks about capturing different events for different needs but is unclear as to what exactly is needed for use as a "minimul set". I would like to use the capture for reporting but do not need all of the events because I am not goi
ng to use the Ostress tool. I just want the minimul set of events to get the most out of reporting... Any help you could offer would be greatly appreciated...[vbcol=seagreen]
|||I used to do that (manually load trace files into SQL tables) before
Microsoft opened up Read80Trace to the whole world. Read80Trace is
very very fast in loading a trace file into tables. For example, it can
load a 750 MB trace file (approximatelt 3.5 million rows in the trace)
and generate an RML output in about 2 minutes or less.
Nothing else that I know of comes anywhere close to this.
John Bell wrote:
> Hi
> The format of trace files seems to be different to SQL 2000, but you can
> work around this by loading the SQL 2005 trace into a table and then
> exporting it back into SQL 2000. You can then use SQL 2000 profile to read
> the table and save it as a trace file to feed into Read80Trace.
> John
>
|||I used to do that (manually load trace files into SQL tables) before
Microsoft opened up Read80Trace to the whole world. Read80Trace is
very very fast in loading a trace file into tables. For example, it can
load a 750 MB trace file (approximatelt 3.5 million rows in the trace)
and generate an RML output in about 2 minutes or less.
Nothing else that I know of comes anywhere close to this.
John Bell wrote:
> Hi
> The format of trace files seems to be different to SQL 2000, but you can
> work around this by loading the SQL 2005 trace into a table and then
> exporting it back into SQL 2000. You can then use SQL 2000 profile to read
> the table and save it as a trace file to feed into Read80Trace.
> John
>
|||it depends on what exactly you are trying to analyze. most imortant
you should include endtime column. with that info, you do not need the
start event. let me know if you need more specific info on what events
/ col to use.
|||But did you use that technique to convert between the SQL 2005 trace files
and SQL 2000?
John
"baddy" wrote:

> I used to do that (manually load trace files into SQL tables) before
> Microsoft opened up Read80Trace to the whole world. Read80Trace is
> very very fast in loading a trace file into tables. For example, it can
> load a 750 MB trace file (approximatelt 3.5 million rows in the trace)
> and generate an RML output in about 2 minutes or less.
> Nothing else that I know of comes anywhere close to this.
>
> John Bell wrote:
>

Friday, March 23, 2012

Read Only Access to Stored Procedures

We do not allow anyone except DBA's the DBO access permission in our
organization for the "production" environment. The programmers get
DataReader/DataWriter access in production, however, they are wanting
read-only access to the stored procedures.
Does anyone know of a why to give them READ ONLY access to stored procedures
?
Thanks for your help.
ColetteThe only permissions you can grant Users WRT SP's is Execute.
Either a user is allowed to execute a SP or not.
I would seriously re-consider Developer Access to production. Developers
should only be in development, and support staff read only production rights
.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Colette" wrote:

> We do not allow anyone except DBA's the DBO access permission in our
> organization for the "production" environment. The programmers get
> DataReader/DataWriter access in production, however, they are wanting
> read-only access to the stored procedures.
> Does anyone know of a why to give them READ ONLY access to stored procedur
es?
> Thanks for your help.
> Colette

Friday, March 9, 2012

RDL File Not Saved

I am using Visual Studio .NET 2003 (with Reporting Services installed), and a
cluster of SQL Server 2000 in a Citrix environment.
I created a Business Inteligence Project, a Shared data source, added a new
report and created a new dataset. I added tables to my Data tab, setup the
relationships, etc.
I Save All and exit VS (without building or deploying the solution). Next
time I come back my Report Data file does not contain the tables I previously
added on. No matter how many tables I add the size of the .rdl file seems to
be 1 kB.
This hapens occasionally only. I could not find a relationship yet but there
are occasions when the rdl file does save properly and thus I don't loose all
my work.
Any suggestions would be greatly appreciated!
Thanks
SorinTry to switch to Layout view before saving your project.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"SOPONL" <SOPONL@.discussions.microsoft.com> wrote in message
news:891ADFC9-F003-4789-94E6-85214AF9AF02@.microsoft.com...
>I am using Visual Studio .NET 2003 (with Reporting Services installed), and
>a
> cluster of SQL Server 2000 in a Citrix environment.
> I created a Business Inteligence Project, a Shared data source, added a
> new
> report and created a new dataset. I added tables to my Data tab, setup the
> relationships, etc.
> I Save All and exit VS (without building or deploying the solution). Next
> time I come back my Report Data file does not contain the tables I
> previously
> added on. No matter how many tables I add the size of the .rdl file seems
> to
> be 1 kB.
> This hapens occasionally only. I could not find a relationship yet but
> there
> are occasions when the rdl file does save properly and thus I don't loose
> all
> my work.
> Any suggestions would be greatly appreciated!
> Thanks
> Sorin|||I've switched to Layout, saved the project and closed VS. Then I re-open the
project; the tables were still not there.
"Lev Semenets [MSFT]" wrote:
> Try to switch to Layout view before saving your project.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "SOPONL" <SOPONL@.discussions.microsoft.com> wrote in message
> news:891ADFC9-F003-4789-94E6-85214AF9AF02@.microsoft.com...
> >I am using Visual Studio .NET 2003 (with Reporting Services installed), and
> >a
> > cluster of SQL Server 2000 in a Citrix environment.
> >
> > I created a Business Inteligence Project, a Shared data source, added a
> > new
> > report and created a new dataset. I added tables to my Data tab, setup the
> > relationships, etc.
> >
> > I Save All and exit VS (without building or deploying the solution). Next
> > time I come back my Report Data file does not contain the tables I
> > previously
> > added on. No matter how many tables I add the size of the .rdl file seems
> > to
> > be 1 kB.
> >
> > This hapens occasionally only. I could not find a relationship yet but
> > there
> > are occasions when the rdl file does save properly and thus I don't loose
> > all
> > my work.
> >
> > Any suggestions would be greatly appreciated!
> >
> > Thanks
> > Sorin
>
>|||In the Data tab I always click in the top section until I see the "*" after
the file name and then right-click the tab to save it.
"SOPONL" wrote:
> I've switched to Layout, saved the project and closed VS. Then I re-open the
> project; the tables were still not there.
> "Lev Semenets [MSFT]" wrote:
> > Try to switch to Layout view before saving your project.
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> > "SOPONL" <SOPONL@.discussions.microsoft.com> wrote in message
> > news:891ADFC9-F003-4789-94E6-85214AF9AF02@.microsoft.com...
> > >I am using Visual Studio .NET 2003 (with Reporting Services installed), and
> > >a
> > > cluster of SQL Server 2000 in a Citrix environment.
> > >
> > > I created a Business Inteligence Project, a Shared data source, added a
> > > new
> > > report and created a new dataset. I added tables to my Data tab, setup the
> > > relationships, etc.
> > >
> > > I Save All and exit VS (without building or deploying the solution). Next
> > > time I come back my Report Data file does not contain the tables I
> > > previously
> > > added on. No matter how many tables I add the size of the .rdl file seems
> > > to
> > > be 1 kB.
> > >
> > > This hapens occasionally only. I could not find a relationship yet but
> > > there
> > > are occasions when the rdl file does save properly and thus I don't loose
> > > all
> > > my work.
> > >
> > > Any suggestions would be greatly appreciated!
> > >
> > > Thanks
> > > Sorin
> >
> >
> >

Saturday, February 25, 2012

RDA Pull Error table

My dev environment: VS2005, SQLServer Mobile, SQLServer 2005 server db, PPC windows app.

Having a problem with pull. First pull works fine. I request an error table from the pull. When I need to repull, I drop the table, but if I try to programmatically delete the error table, I get the message that the table has restricted DDL operations allowed. Apparently Drop is not allowed. Sometimes dropping the main table deletes the error table, sometimes it doesn't. If I try to repull and the error table is there, the pull fails.

I've tried "flushing" my cache by closing my connection and reopening, but that doesn't work.

Any ideas?

I have a similar problem--I have primary key indexes on the table I'm trying to pull which DONT go away when the table is dropped. I can't delete them because they give me the same "restricted DDL operations" error, and the pull fails when they are around.

I posted about it a while back, but never did get a reasonable response. Right now I'm deleting my entire database each time I do a pull, which is a very ham-fisted way of doing it, and it's awful slow. Unfortunately, no one else seems to be able to help...

-Kevin

|||

Just to narrow down the problem can you do the following:

Before dropping the main table can you soft-reset the device and drop the main table? I am really interested to know the root cause of the problem. Also please note that, just clicking ok on any device app does not actually close the app but pushes it to background. To termainte the app, you need to go to Start Menu => Settings => System => Memory => Running Programs ==> Stop the process

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

Whether I drop it from my program or from QA, I sometimes get the error table deleted, sometimes not. That's after a reset. I'm pretty sure I've got my app closing correctly now, which it wasn't before, but now if I look at memory as you suggest, there is no vestige of my program hanging around. I finally decided I didn't really need the error table anyway and so have excluded it from my pull arguments.

However, a related problem promises to be an even bigger headache. Occasionally, dropping the main table does not manage to delete the appropriate entries in __SysRDASubscriptions, so that when I go to pull that table again, even though the actual table has been dropped, the pull informs me that it can't upupdate __SysRDASubscriptions before of a dup entry (error 25016). And guess what, __SysRDASubscriptions is read-only, so I can't "delete from" either. The only workaround I can think of is to backup the tables I need in my .sdf, trash the original and create a new db - a big hack to say the least.

As to what causes the entry not to be deleted, sometimes the database is corrupt (.Verify returns false), but repairing doesn't take care of __SysRDASubscriptions dirty entry.

Any ideas?

|||

Can you please give your email id so that I can contact you offline for faster conversation!

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||hi Laxmi, did you get my return email or do I have to post my email address here?|||

Hi,

I have the same problem also, I am trying to delete the entry from __sysrdasubscriptions table but its coming back with read only error...any advice on how to accomplish this. What i really wanted to do is drop the table and recreate...since the deleted table is not being deleted from sysrdasubscriptions i need to do it manually...Please help...

michael

|||This happens intermittently in my app. Sometimes the delete table takes care of the sysrdasubscriptions row and sometimes it doesn't. I'm closing down my connection before I do the delete just to make sure there are no pending updates waiting, but I still get the problem. The worst part is that I can't reproduce it consistently. How about in your case - does it always fail to delete the row?|||

Hi,

In my case, when i drop the table the entries from the sysrdasubscriptions still remains consistently...it just never deleted but then when i delete the entry it comes back with an error of read only...I am not sure what to do with it...the only solution i can think of is delete the database with a drawback of becoming very slow since it will need to reproduce everything...

best regards,

michael

|||

I thought of deleting the db too but that's definitely a last resort.

|||

Hello Laxmi - did you get my response to your email.

This seems like a serious problem. Hoping you have some ideas other than deleting the database.

|||

Sorry guys I am totally lost in my work. I am really sorry about that.

Please send across the repro details along with the repro database at our BLOG http://blogs.msdn.com/sqlmobile/.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

Hi

I am getting the exact same problem.

Any news on a fix for this?

Regards Andrew

|||Having had ZERO help after promises and promises

from Microsoft, we finally took the hard core approach and delete the

entire database, so as to ensure the deletion of the subscriptions

info.

As usual, MS releases beta, well more like alpha, products to the

marketplace and relies on its market domination to keep even the most

disgruntled of customers in their camp. However, we have deployed

this as only a temporary solution. In three months, we will be

rearchitecting with a Java solution, with a prototype already working

more reliably than the MS ***. This was only one of many

disappointments for us from MS, and so now we are turning the corner

and going with a more reliable framework, and just better solutions in

general. Too bad MS feels that don't really have to deliver

anything of quality anymore. No wonder their stock is a dinosaur

stuck in the toilet.

Good luck to you...|||

Hi Braden,

This problem is in locating the other sql mobile dlls while dropping the table.

This problem does not appear if you have all of the following in a single directory:

1) SQL Mobile product DLLs

2) SQL Mobile tools (such as ISQLW30.EXE in case you are using it!)

3) Customer application which uses RDA

4) Any other binary that is using SQL Mobile binaries

Please be patient while we work on the problem.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Ev, Microsoft Corporation

RDA Pull Error table

My dev environment: VS2005, SQLServer Mobile, SQLServer 2005 server db, PPC windows app.

Having a problem with pull. First pull works fine. I request an error table from the pull. When I need to repull, I drop the table, but if I try to programmatically delete the error table, I get the message that the table has restricted DDL operations allowed. Apparently Drop is not allowed. Sometimes dropping the main table deletes the error table, sometimes it doesn't. If I try to repull and the error table is there, the pull fails.

I've tried "flushing" my cache by closing my connection and reopening, but that doesn't work.

Any ideas?

I have a similar problem--I have primary key indexes on the table I'm trying to pull which DONT go away when the table is dropped. I can't delete them because they give me the same "restricted DDL operations" error, and the pull fails when they are around.

I posted about it a while back, but never did get a reasonable response. Right now I'm deleting my entire database each time I do a pull, which is a very ham-fisted way of doing it, and it's awful slow. Unfortunately, no one else seems to be able to help...

-Kevin

|||

Just to narrow down the problem can you do the following:

Before dropping the main table can you soft-reset the device and drop the main table? I am really interested to know the root cause of the problem. Also please note that, just clicking ok on any device app does not actually close the app but pushes it to background. To termainte the app, you need to go to Start Menu => Settings => System => Memory => Running Programs ==> Stop the process

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

Whether I drop it from my program or from QA, I sometimes get the error table deleted, sometimes not. That's after a reset. I'm pretty sure I've got my app closing correctly now, which it wasn't before, but now if I look at memory as you suggest, there is no vestige of my program hanging around. I finally decided I didn't really need the error table anyway and so have excluded it from my pull arguments.

However, a related problem promises to be an even bigger headache. Occasionally, dropping the main table does not manage to delete the appropriate entries in __SysRDASubscriptions, so that when I go to pull that table again, even though the actual table has been dropped, the pull informs me that it can't upupdate __SysRDASubscriptions before of a dup entry (error 25016). And guess what, __SysRDASubscriptions is read-only, so I can't "delete from" either. The only workaround I can think of is to backup the tables I need in my .sdf, trash the original and create a new db - a big hack to say the least.

As to what causes the entry not to be deleted, sometimes the database is corrupt (.Verify returns false), but repairing doesn't take care of __SysRDASubscriptions dirty entry.

Any ideas?

|||

Can you please give your email id so that I can contact you offline for faster conversation!

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||hi Laxmi, did you get my return email or do I have to post my email address here?|||

Hi,

I have the same problem also, I am trying to delete the entry from __sysrdasubscriptions table but its coming back with read only error...any advice on how to accomplish this. What i really wanted to do is drop the table and recreate...since the deleted table is not being deleted from sysrdasubscriptions i need to do it manually...Please help...

michael

|||This happens intermittently in my app. Sometimes the delete table takes care of the sysrdasubscriptions row and sometimes it doesn't. I'm closing down my connection before I do the delete just to make sure there are no pending updates waiting, but I still get the problem. The worst part is that I can't reproduce it consistently. How about in your case - does it always fail to delete the row?|||

Hi,

In my case, when i drop the table the entries from the sysrdasubscriptions still remains consistently...it just never deleted but then when i delete the entry it comes back with an error of read only...I am not sure what to do with it...the only solution i can think of is delete the database with a drawback of becoming very slow since it will need to reproduce everything...

best regards,

michael

|||

I thought of deleting the db too but that's definitely a last resort.

|||

Hello Laxmi - did you get my response to your email.

This seems like a serious problem. Hoping you have some ideas other than deleting the database.

|||

Sorry guys I am totally lost in my work. I am really sorry about that.

Please send across the repro details along with the repro database at our BLOG http://blogs.msdn.com/sqlmobile/.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

Hi

I am getting the exact same problem.

Any news on a fix for this?

Regards Andrew

|||Having had ZERO help after promises and promises

from Microsoft, we finally took the hard core approach and delete the

entire database, so as to ensure the deletion of the subscriptions

info.

As usual, MS releases beta, well more like alpha, products to the

marketplace and relies on its market domination to keep even the most

disgruntled of customers in their camp. However, we have deployed

this as only a temporary solution. In three months, we will be

rearchitecting with a Java solution, with a prototype already working

more reliably than the MS ***. This was only one of many

disappointments for us from MS, and so now we are turning the corner

and going with a more reliable framework, and just better solutions in

general. Too bad MS feels that don't really have to deliver

anything of quality anymore. No wonder their stock is a dinosaur

stuck in the toilet.

Good luck to you...|||

Hi Braden,

This problem is in locating the other sql mobile dlls while dropping the table.

This problem does not appear if you have all of the following in a single directory:

1) SQL Mobile product DLLs

2) SQL Mobile tools (such as ISQLW30.EXE in case you are using it!)

3) Customer application which uses RDA

4) Any other binary that is using SQL Mobile binaries

Please be patient while we work on the problem.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Ev, Microsoft Corporation

RDA Pull Error table

My dev environment: VS2005, SQLServer Mobile, SQLServer 2005 server db, PPC windows app.

Having a problem with pull. First pull works fine. I request an error table from the pull. When I need to repull, I drop the table, but if I try to programmatically delete the error table, I get the message that the table has restricted DDL operations allowed. Apparently Drop is not allowed. Sometimes dropping the main table deletes the error table, sometimes it doesn't. If I try to repull and the error table is there, the pull fails.

I've tried "flushing" my cache by closing my connection and reopening, but that doesn't work.

Any ideas?

I have a similar problem--I have primary key indexes on the table I'm trying to pull which DONT go away when the table is dropped. I can't delete them because they give me the same "restricted DDL operations" error, and the pull fails when they are around.

I posted about it a while back, but never did get a reasonable response. Right now I'm deleting my entire database each time I do a pull, which is a very ham-fisted way of doing it, and it's awful slow. Unfortunately, no one else seems to be able to help...

-Kevin

|||

Just to narrow down the problem can you do the following:

Before dropping the main table can you soft-reset the device and drop the main table? I am really interested to know the root cause of the problem. Also please note that, just clicking ok on any device app does not actually close the app but pushes it to background. To termainte the app, you need to go to Start Menu => Settings => System => Memory => Running Programs ==> Stop the process

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

Whether I drop it from my program or from QA, I sometimes get the error table deleted, sometimes not. That's after a reset. I'm pretty sure I've got my app closing correctly now, which it wasn't before, but now if I look at memory as you suggest, there is no vestige of my program hanging around. I finally decided I didn't really need the error table anyway and so have excluded it from my pull arguments.

However, a related problem promises to be an even bigger headache. Occasionally, dropping the main table does not manage to delete the appropriate entries in __SysRDASubscriptions, so that when I go to pull that table again, even though the actual table has been dropped, the pull informs me that it can't upupdate __SysRDASubscriptions before of a dup entry (error 25016). And guess what, __SysRDASubscriptions is read-only, so I can't "delete from" either. The only workaround I can think of is to backup the tables I need in my .sdf, trash the original and create a new db - a big hack to say the least.

As to what causes the entry not to be deleted, sometimes the database is corrupt (.Verify returns false), but repairing doesn't take care of __SysRDASubscriptions dirty entry.

Any ideas?

|||

Can you please give your email id so that I can contact you offline for faster conversation!

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||hi Laxmi, did you get my return email or do I have to post my email address here?|||

Hi,

I have the same problem also, I am trying to delete the entry from __sysrdasubscriptions table but its coming back with read only error...any advice on how to accomplish this. What i really wanted to do is drop the table and recreate...since the deleted table is not being deleted from sysrdasubscriptions i need to do it manually...Please help...

michael

|||This happens intermittently in my app. Sometimes the delete table takes care of the sysrdasubscriptions row and sometimes it doesn't. I'm closing down my connection before I do the delete just to make sure there are no pending updates waiting, but I still get the problem. The worst part is that I can't reproduce it consistently. How about in your case - does it always fail to delete the row?|||

Hi,

In my case, when i drop the table the entries from the sysrdasubscriptions still remains consistently...it just never deleted but then when i delete the entry it comes back with an error of read only...I am not sure what to do with it...the only solution i can think of is delete the database with a drawback of becoming very slow since it will need to reproduce everything...

best regards,

michael

|||

I thought of deleting the db too but that's definitely a last resort.

|||

Hello Laxmi - did you get my response to your email.

This seems like a serious problem. Hoping you have some ideas other than deleting the database.

|||

Sorry guys I am totally lost in my work. I am really sorry about that.

Please send across the repro details along with the repro database at our BLOG http://blogs.msdn.com/sqlmobile/.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

Hi

I am getting the exact same problem.

Any news on a fix for this?

Regards Andrew

|||Having had ZERO help after promises and promises from Microsoft, we finally took the hard core approach and delete the entire database, so as to ensure the deletion of the subscriptions info.
As usual, MS releases beta, well more like alpha, products to the marketplace and relies on its market domination to keep even the most disgruntled of customers in their camp. However, we have deployed this as only a temporary solution. In three months, we will be rearchitecting with a Java solution, with a prototype already working more reliably than the MS ***. This was only one of many disappointments for us from MS, and so now we are turning the corner and going with a more reliable framework, and just better solutions in general. Too bad MS feels that don't really have to deliver anything of quality anymore. No wonder their stock is a dinosaur stuck in the toilet.
Good luck to you...
|||

Hi Braden,

This problem is in locating the other sql mobile dlls while dropping the table.

This problem does not appear if you have all of the following in a single directory:

1) SQL Mobile product DLLs

2) SQL Mobile tools (such as ISQLW30.EXE in case you are using it!)

3) Customer application which uses RDA

4) Any other binary that is using SQL Mobile binaries

Please be patient while we work on the problem.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Ev, Microsoft Corporation

RDA Pull Error table

My dev environment: VS2005, SQLServer Mobile, SQLServer 2005 server db, PPC windows app.

Having a problem with pull. First pull works fine. I request an error table from the pull. When I need to repull, I drop the table, but if I try to programmatically delete the error table, I get the message that the table has restricted DDL operations allowed. Apparently Drop is not allowed. Sometimes dropping the main table deletes the error table, sometimes it doesn't. If I try to repull and the error table is there, the pull fails.

I've tried "flushing" my cache by closing my connection and reopening, but that doesn't work.

Any ideas?

I have a similar problem--I have primary key indexes on the table I'm trying to pull which DONT go away when the table is dropped. I can't delete them because they give me the same "restricted DDL operations" error, and the pull fails when they are around.

I posted about it a while back, but never did get a reasonable response. Right now I'm deleting my entire database each time I do a pull, which is a very ham-fisted way of doing it, and it's awful slow. Unfortunately, no one else seems to be able to help...

-Kevin

|||

Just to narrow down the problem can you do the following:

Before dropping the main table can you soft-reset the device and drop the main table? I am really interested to know the root cause of the problem. Also please note that, just clicking ok on any device app does not actually close the app but pushes it to background. To termainte the app, you need to go to Start Menu => Settings => System => Memory => Running Programs ==> Stop the process

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

Whether I drop it from my program or from QA, I sometimes get the error table deleted, sometimes not. That's after a reset. I'm pretty sure I've got my app closing correctly now, which it wasn't before, but now if I look at memory as you suggest, there is no vestige of my program hanging around. I finally decided I didn't really need the error table anyway and so have excluded it from my pull arguments.

However, a related problem promises to be an even bigger headache. Occasionally, dropping the main table does not manage to delete the appropriate entries in __SysRDASubscriptions, so that when I go to pull that table again, even though the actual table has been dropped, the pull informs me that it can't upupdate __SysRDASubscriptions before of a dup entry (error 25016). And guess what, __SysRDASubscriptions is read-only, so I can't "delete from" either. The only workaround I can think of is to backup the tables I need in my .sdf, trash the original and create a new db - a big hack to say the least.

As to what causes the entry not to be deleted, sometimes the database is corrupt (.Verify returns false), but repairing doesn't take care of __SysRDASubscriptions dirty entry.

Any ideas?

|||

Can you please give your email id so that I can contact you offline for faster conversation!

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||hi Laxmi, did you get my return email or do I have to post my email address here?|||

Hi,

I have the same problem also, I am trying to delete the entry from __sysrdasubscriptions table but its coming back with read only error...any advice on how to accomplish this. What i really wanted to do is drop the table and recreate...since the deleted table is not being deleted from sysrdasubscriptions i need to do it manually...Please help...

michael

|||This happens intermittently in my app. Sometimes the delete table takes care of the sysrdasubscriptions row and sometimes it doesn't. I'm closing down my connection before I do the delete just to make sure there are no pending updates waiting, but I still get the problem. The worst part is that I can't reproduce it consistently. How about in your case - does it always fail to delete the row?|||

Hi,

In my case, when i drop the table the entries from the sysrdasubscriptions still remains consistently...it just never deleted but then when i delete the entry it comes back with an error of read only...I am not sure what to do with it...the only solution i can think of is delete the database with a drawback of becoming very slow since it will need to reproduce everything...

best regards,

michael

|||

I thought of deleting the db too but that's definitely a last resort.

|||

Hello Laxmi - did you get my response to your email.

This seems like a serious problem. Hoping you have some ideas other than deleting the database.

|||

Sorry guys I am totally lost in my work. I am really sorry about that.

Please send across the repro details along with the repro database at our BLOG http://blogs.msdn.com/sqlmobile/.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

Hi

I am getting the exact same problem.

Any news on a fix for this?

Regards Andrew

|||Having had ZERO help after promises and promises from Microsoft, we finally took the hard core approach and delete the entire database, so as to ensure the deletion of the subscriptions info.
As usual, MS releases beta, well more like alpha, products to the marketplace and relies on its market domination to keep even the most disgruntled of customers in their camp. However, we have deployed this as only a temporary solution. In three months, we will be rearchitecting with a Java solution, with a prototype already working more reliably than the MS ***. This was only one of many disappointments for us from MS, and so now we are turning the corner and going with a more reliable framework, and just better solutions in general. Too bad MS feels that don't really have to deliver anything of quality anymore. No wonder their stock is a dinosaur stuck in the toilet.
Good luck to you...
|||

Hi Braden,

This problem is in locating the other sql mobile dlls while dropping the table.

This problem does not appear if you have all of the following in a single directory:

1) SQL Mobile product DLLs

2) SQL Mobile tools (such as ISQLW30.EXE in case you are using it!)

3) Customer application which uses RDA

4) Any other binary that is using SQL Mobile binaries

Please be patient while we work on the problem.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Ev, Microsoft Corporation

RDA Pull Error table

My dev environment: VS2005, SQLServer Mobile, SQLServer 2005 server db, PPC windows app.

Having a problem with pull. First pull works fine. I request an error table from the pull. When I need to repull, I drop the table, but if I try to programmatically delete the error table, I get the message that the table has restricted DDL operations allowed. Apparently Drop is not allowed. Sometimes dropping the main table deletes the error table, sometimes it doesn't. If I try to repull and the error table is there, the pull fails.

I've tried "flushing" my cache by closing my connection and reopening, but that doesn't work.

Any ideas?

I have a similar problem--I have primary key indexes on the table I'm trying to pull which DONT go away when the table is dropped. I can't delete them because they give me the same "restricted DDL operations" error, and the pull fails when they are around.

I posted about it a while back, but never did get a reasonable response. Right now I'm deleting my entire database each time I do a pull, which is a very ham-fisted way of doing it, and it's awful slow. Unfortunately, no one else seems to be able to help...

-Kevin

|||

Just to narrow down the problem can you do the following:

Before dropping the main table can you soft-reset the device and drop the main table? I am really interested to know the root cause of the problem. Also please note that, just clicking ok on any device app does not actually close the app but pushes it to background. To termainte the app, you need to go to Start Menu => Settings => System => Memory => Running Programs ==> Stop the process

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

Whether I drop it from my program or from QA, I sometimes get the error table deleted, sometimes not. That's after a reset. I'm pretty sure I've got my app closing correctly now, which it wasn't before, but now if I look at memory as you suggest, there is no vestige of my program hanging around. I finally decided I didn't really need the error table anyway and so have excluded it from my pull arguments.

However, a related problem promises to be an even bigger headache. Occasionally, dropping the main table does not manage to delete the appropriate entries in __SysRDASubscriptions, so that when I go to pull that table again, even though the actual table has been dropped, the pull informs me that it can't upupdate __SysRDASubscriptions before of a dup entry (error 25016). And guess what, __SysRDASubscriptions is read-only, so I can't "delete from" either. The only workaround I can think of is to backup the tables I need in my .sdf, trash the original and create a new db - a big hack to say the least.

As to what causes the entry not to be deleted, sometimes the database is corrupt (.Verify returns false), but repairing doesn't take care of __SysRDASubscriptions dirty entry.

Any ideas?

|||

Can you please give your email id so that I can contact you offline for faster conversation!

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||hi Laxmi, did you get my return email or do I have to post my email address here?|||

Hi,

I have the same problem also, I am trying to delete the entry from __sysrdasubscriptions table but its coming back with read only error...any advice on how to accomplish this. What i really wanted to do is drop the table and recreate...since the deleted table is not being deleted from sysrdasubscriptions i need to do it manually...Please help...

michael

|||This happens intermittently in my app. Sometimes the delete table takes care of the sysrdasubscriptions row and sometimes it doesn't. I'm closing down my connection before I do the delete just to make sure there are no pending updates waiting, but I still get the problem. The worst part is that I can't reproduce it consistently. How about in your case - does it always fail to delete the row?|||

Hi,

In my case, when i drop the table the entries from the sysrdasubscriptions still remains consistently...it just never deleted but then when i delete the entry it comes back with an error of read only...I am not sure what to do with it...the only solution i can think of is delete the database with a drawback of becoming very slow since it will need to reproduce everything...

best regards,

michael

|||

I thought of deleting the db too but that's definitely a last resort.

|||

Hello Laxmi - did you get my response to your email.

This seems like a serious problem. Hoping you have some ideas other than deleting the database.

|||

Sorry guys I am totally lost in my work. I am really sorry about that.

Please send across the repro details along with the repro database at our BLOG http://blogs.msdn.com/sqlmobile/.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

Hi

I am getting the exact same problem.

Any news on a fix for this?

Regards Andrew

|||Having had ZERO help after promises and promises

from Microsoft, we finally took the hard core approach and delete the

entire database, so as to ensure the deletion of the subscriptions

info.

As usual, MS releases beta, well more like alpha, products to the

marketplace and relies on its market domination to keep even the most

disgruntled of customers in their camp. However, we have deployed

this as only a temporary solution. In three months, we will be

rearchitecting with a Java solution, with a prototype already working

more reliably than the MS ***. This was only one of many

disappointments for us from MS, and so now we are turning the corner

and going with a more reliable framework, and just better solutions in

general. Too bad MS feels that don't really have to deliver

anything of quality anymore. No wonder their stock is a dinosaur

stuck in the toilet.

Good luck to you...|||

Hi Braden,

This problem is in locating the other sql mobile dlls while dropping the table.

This problem does not appear if you have all of the following in a single directory:

1) SQL Mobile product DLLs

2) SQL Mobile tools (such as ISQLW30.EXE in case you are using it!)

3) Customer application which uses RDA

4) Any other binary that is using SQL Mobile binaries

Please be patient while we work on the problem.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Ev, Microsoft Corporation

RDA Pull Error table

My dev environment: VS2005, SQLServer Mobile, SQLServer 2005 server db, PPC windows app.

Having a problem with pull. First pull works fine. I request an error table from the pull. When I need to repull, I drop the table, but if I try to programmatically delete the error table, I get the message that the table has restricted DDL operations allowed. Apparently Drop is not allowed. Sometimes dropping the main table deletes the error table, sometimes it doesn't. If I try to repull and the error table is there, the pull fails.

I've tried "flushing" my cache by closing my connection and reopening, but that doesn't work.

Any ideas?

I have a similar problem--I have primary key indexes on the table I'm trying to pull which DONT go away when the table is dropped. I can't delete them because they give me the same "restricted DDL operations" error, and the pull fails when they are around.

I posted about it a while back, but never did get a reasonable response. Right now I'm deleting my entire database each time I do a pull, which is a very ham-fisted way of doing it, and it's awful slow. Unfortunately, no one else seems to be able to help...

-Kevin

|||

Just to narrow down the problem can you do the following:

Before dropping the main table can you soft-reset the device and drop the main table? I am really interested to know the root cause of the problem. Also please note that, just clicking ok on any device app does not actually close the app but pushes it to background. To termainte the app, you need to go to Start Menu => Settings => System => Memory => Running Programs ==> Stop the process

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

Whether I drop it from my program or from QA, I sometimes get the error table deleted, sometimes not. That's after a reset. I'm pretty sure I've got my app closing correctly now, which it wasn't before, but now if I look at memory as you suggest, there is no vestige of my program hanging around. I finally decided I didn't really need the error table anyway and so have excluded it from my pull arguments.

However, a related problem promises to be an even bigger headache. Occasionally, dropping the main table does not manage to delete the appropriate entries in __SysRDASubscriptions, so that when I go to pull that table again, even though the actual table has been dropped, the pull informs me that it can't upupdate __SysRDASubscriptions before of a dup entry (error 25016). And guess what, __SysRDASubscriptions is read-only, so I can't "delete from" either. The only workaround I can think of is to backup the tables I need in my .sdf, trash the original and create a new db - a big hack to say the least.

As to what causes the entry not to be deleted, sometimes the database is corrupt (.Verify returns false), but repairing doesn't take care of __SysRDASubscriptions dirty entry.

Any ideas?

|||

Can you please give your email id so that I can contact you offline for faster conversation!

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||hi Laxmi, did you get my return email or do I have to post my email address here?|||

Hi,

I have the same problem also, I am trying to delete the entry from __sysrdasubscriptions table but its coming back with read only error...any advice on how to accomplish this. What i really wanted to do is drop the table and recreate...since the deleted table is not being deleted from sysrdasubscriptions i need to do it manually...Please help...

michael

|||This happens intermittently in my app. Sometimes the delete table takes care of the sysrdasubscriptions row and sometimes it doesn't. I'm closing down my connection before I do the delete just to make sure there are no pending updates waiting, but I still get the problem. The worst part is that I can't reproduce it consistently. How about in your case - does it always fail to delete the row?|||

Hi,

In my case, when i drop the table the entries from the sysrdasubscriptions still remains consistently...it just never deleted but then when i delete the entry it comes back with an error of read only...I am not sure what to do with it...the only solution i can think of is delete the database with a drawback of becoming very slow since it will need to reproduce everything...

best regards,

michael

|||

I thought of deleting the db too but that's definitely a last resort.

|||

Hello Laxmi - did you get my response to your email.

This seems like a serious problem. Hoping you have some ideas other than deleting the database.

|||

Sorry guys I am totally lost in my work. I am really sorry about that.

Please send across the repro details along with the repro database at our BLOG http://blogs.msdn.com/sqlmobile/.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

Hi

I am getting the exact same problem.

Any news on a fix for this?

Regards Andrew

|||Having had ZERO help after promises and promises from Microsoft, we finally took the hard core approach and delete the entire database, so as to ensure the deletion of the subscriptions info.
As usual, MS releases beta, well more like alpha, products to the marketplace and relies on its market domination to keep even the most disgruntled of customers in their camp. However, we have deployed this as only a temporary solution. In three months, we will be rearchitecting with a Java solution, with a prototype already working more reliably than the MS ***. This was only one of many disappointments for us from MS, and so now we are turning the corner and going with a more reliable framework, and just better solutions in general. Too bad MS feels that don't really have to deliver anything of quality anymore. No wonder their stock is a dinosaur stuck in the toilet.
Good luck to you...
|||

Hi Braden,

This problem is in locating the other sql mobile dlls while dropping the table.

This problem does not appear if you have all of the following in a single directory:

1) SQL Mobile product DLLs

2) SQL Mobile tools (such as ISQLW30.EXE in case you are using it!)

3) Customer application which uses RDA

4) Any other binary that is using SQL Mobile binaries

Please be patient while we work on the problem.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Ev, Microsoft Corporation

Monday, February 20, 2012

raw file destination and environment variables

when using a raw file destination it would be nice to be able to use an environment variable for the filename property.

like

%my_extract%\data.txt

instead of

c:\my_extract\data.txt

Could you turn your screen round a bit... ...no, sorry, still cannot see it from here. Could you describe which OK button it is, any errors you may have when clicking, and perhaps briefly what lead up to this point.

|||

You could use the script task to define a SSIS variable, storing the file name, built using the environment variable. Then you can use this variable in Raw adapters by using the File Name from Variable access mode.

HTH.

|||

have you actually tried that?

|||

Now, I have. It worked fine for me.

Have you had problems with it?

|||How did you do it, there isn't an expressions setting for raw sources/destinations. What do you do to get the filename to be based on a variable?|||Raw file adapters have an AccessMode property, which allows you to enter a filename or a variable name. Variables can obviously use expressions.|||Doh, looked everywhere for that and ti was right under my nose.|||

not yet. I will give it a try today.

you should post some code and a sample usage.

|||

There is the AccessMode property on the raw adapters; change it to "File name from variable" and set your variable to the FileNameVariable property.

Thanks.

|||

Here is how I did it:

- Define RawFileName variable of type string on the package level

- Add the Script Task and set its ReadWriteVariables property to "RawFileName" and the script like this:

Public Sub Main()

Dts.Variables("RawFileName").Value = System.Environment.GetEnvironmentVariable("<your_env_var>") + "\<your_file_name>"

Dts.TaskResult = Dts.Results.Success

End Sub

- Add the Data Flow Task after the Script Task, define your data flow with the Raw File Destination and set its file name to come from the RawFileName variable, as explained in the previous messages.

HTH.

|||

not working for me.

so you actually ran it. it worked? seriously you actually ran it and it created the file you specified?

I create the variable at the package level.

I create the script task and stick the code in there.

I go to my advanced editor for raw file destination.

select accessmode: file name from variable

filenamevariable: user::rawfilename

it keeps telling me error at dataflow task (raw file destination[23]: the file name is not properly specified. supply the path and name to the raw file either directly in the file name property or by specifying a variable in the filenamevariable property.

what gives?

|||

Have you investigated why it is not working? If the file name is invalid, is the variable getting set correctly? Some ideas-

Set a breakpoint on the PreExecute event of the Data Flow and when broken drag the Rawfilename variable into the Watch window. Examine the value.

Add some breakpoints into the Script Task and examine the values as you step through the code.

|||the gui will not let me click the ok button|||

I can delete my raw file destination out of the data flow and put a break point on the data flow task and look at my variable.

it looks like a file name. correctly formatted in all it's glory.

user::RawFileName c:\\inetpub\\wwwroot\\a.txt

looks like a good file name to me?

why does the gui insist it's not a valid file name?