Visual Studio 2005’s Typed DataSet is pretty cool. It gives you good control of what the relations should be and it pretty much mimics a table in the database. I love it. But one thing I hate about that is when you serialize your Typed DataSet your XML looks not up to the mark of what you want.

It does serves the purpose but it has all sorts of primary key/foreign key references that are serialized into the XML that at times we don’t want. Rather what we want is a nested XML structure that meaningfully makes sense if you wear that XML glass.

Adding an XSD file to your project won’t help right away as VSNET 2005 doesn’t directly generate dataset (.Designer.cs file) out of it. But, to our rescue, there is a work around to get VSNET 2005 generate typed-dataset from an XSD file. Here is what you should do,

• Select the XSD file you want VSNET 2005 to generate typed-dataset from
• Go into the XSD file’s properties
• Set the "Build Action" to "Content"
• Set the "Custom Tool" to point to "MSDataSetGenerator"

And that’s it. The next time you save the XSD file you

I got this error from one of my ASP.NET web services when I tried to fetch some data from a remote database. I tried searching online for a possible fix to this issue but found none to be convincing and so thought of publishing the solution that resolved the issue.

Please note that this solution may only be effective if you are debugging your ASP.NET page/web service and are manually attaching the worker process.

1. Attach to the worker process.

2. With the aspnet_wp.exe highlighted hit the “Select…” button at the top right hand side.

You will get the “Select Code Type” dialog with the “Automatically determine the type of code to debug” selected. Now for ASP.NET to use the “Managed” code type by checking the “Managed” checkbox.

Try it again and it should work without the “EXECUTE permission denied on object ’sp_sdidebug’, database ‘master’, owner ‘dbo’.” error.

Hope it helps. Let me know of any issues or alternate solutions in comments.