Thursday, August 31, 2006
Monday, August 28, 2006
Sunday, August 27, 2006
Saturday, August 26, 2006
When this parameter is specified, SQL Express will create another instance of the sqlservr.exe process on the client. This process is running in the security context of the currently logged on user. The connection object passed back to the client is connected to this new user child instance, running as a client process in the user's security context.
More details about User Instances? Read this excellent article on msdn: Working with User Instances
For monitoring purposes (what's going on under the hood, troubleshooting and more), the SQL Server Profiler acts as a big time safer. The Profiler is able to read and display all the traffic between the client (e.g. a custom-application, SQL Management Studio etc.) and the SQL Server. Just attach the Profiler to a running SQL Server instance.
But how to attach to a 'user instance', where you don't have a well known instance name?
First, query the master database from SQL Express as follows:
There you get the named pipes per instance. You get the heart-beat as well: alive or dead (if the Lifetime of a User Instance Connection has timed out; default is 60 minutes).
Second, connect with the pipe (just alive instances can be connected):
Third, get the traffic, sniff, profile...
You get the Profiler together with Workgroup-, Standard- and Enterprise edition.
SQL Server Management Studio / SQL Server Management Express
This solution will work for SQL Server Management Studio as well:
The Management Studio does display all attached Databases(in my case AspNetDB.MDF and People.MDF). - There is the free Version SQL Server Management Studio Express.
Local on my dev-machine, I have SQL2k5, SQLExpress nad SQL2k installed and by default, this services are not started when the OS starts. I don't need SQLServer every day, so they shouldn't block memory.
Thanks to this free tool, it's handy and easy to manage (start, pause, stop) the different SQLServices on the different SQLServers.
This Tool and more codes and articles you will find at http://www.sqldbatips.com/
Thursday, August 24, 2006
After you have installed the software, just move the cursor into properties and methods and call the "Document this" command either using the context menu or by pressing the hotkey (if you assigned one).
Here is a sample, where all the comment is generated by GhostDoc:
Wednesday, August 23, 2006
- New Templates
- Comfortable Template customizing
- Mutliple authors
- Private accessible blog
- Support for RSS 2.0, Atom 1.0
- Updated Dashboard
- Instant publishing
Take a tour: http://www.blogger.com/beta-tour.g
Here is the link "HowTo Migrate to Blogger Beta": http://www.blogger.com/migrate-login.do
Interested in Google data API: http://code.blogger.com
This Blog is already migrated to Blogger Beta. One disadvantage @ the moment: The HTML-Template can not changed manually, so I could not migrate stuff like Hit Counter and additional inserted HTML. - But support for this is promised and should coming soon...
But... during the setup at the customer company, we couldn't connect with the admin-user created by our VB-Script. Error-Message: 'Credentials not valid'. What happended!?
There were local policies installed, and the admin-user password didn't meet the minimal requirements, so the account was automatically disabled, without any message!
That's okay from the security point of view. But f****** hard to debug for a developer, escpecially with error messages like 'Credentials not valid'. And a kind of plain-text adsi-editor with hundrets of attributes:
After resetting the attribut "msDS-UserAccountDisabled" to false, everthing worked as expected.
Interested in more information? http://en.wikipedia.org/wiki/Hattrick
Wednesday, August 16, 2006
Next-Generation Data Access: Making the Conceptual Level Real:
Sunday, August 13, 2006
Easy generated Source Code Documentation out of the xml-comments is now possible with the new MS Tool Sandcastle. Till now, NDoc was the first joice for me. But Sandcastle sounds like a real alternative - especially because of real .NET 2.0 support.
Enable managed class library developers throughout the world to easily create accurate, informative documentation with a common look and feel.
Sandcastle is used internally to build .Net Framework documentation.
- Produces quality, comprehensive, familiar MSDN-like documentation.
- Works with or without authored comments.
- Supports Generics and .NET Framework 2.0
- Sandcastle MrefBuilder generates reflection xml file
- Sandcastle Build Assembler includes syntax generation, transformation..etc
Thursday, August 10, 2006
Here a solution to display the current size of the ViewState inside the browsers statusbar:
protected override void OnPreRenderComplete(EventArgs e)
"<script>window.status = 'ViewState: ' + document.forms['__VIEWSTATE'].value.length + ' bytes';</script>");
Put this code in your CodeBehind or in your Web-Base-Page (a page derived from System.Web.UI.Page).
If you are not happy with your ViewState Size, take a look at ViewState Numbers and Solutions to reduce ViewState Size as documented here. Keeping the ViewState on the Server (e.g. via SessionState) instead of the client is one way.