<?xml version='1.0' encoding='UTF-8'?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-14212809</id><updated>2008-08-25T21:12:57.052-06:00</updated><title type='text'>Another day in the life of a programmer gal.</title><link rel='alternate' type='text/html' href='http://theniceweb.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default?start-index=26&amp;max-results=25'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default'/><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>115</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-14212809.post-296676723588474792</id><published>2008-08-25T21:07:00.002-06:00</published><updated>2008-08-25T21:12:57.062-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='fooling around'/><title type='text'>Love at first sight</title><summary type='text'>
We met at Staples.</summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/08/love-at-first-sight-p.html' title='Love at first sight'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=296676723588474792' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/296676723588474792'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/296676723588474792'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-5601217146966646150</id><published>2008-08-25T20:35:00.002-06:00</published><updated>2008-08-25T20:40:41.135-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='vista'/><title type='text'>Arg! the telnet client is disabled by default in Vista</title><summary type='text'>I'm trying to fix my dad's website, after his gallery suffered a sql injection and his database is no longer with us. I needed to check if port 2077 was open on the server to map a folder as a drive on my windows explorer after a few problems with my ftp connection timing out.
To make the story short, how to enable the telnet client on Vista:
Go to Control Panel.
Go to Programs.
Go to Program and</summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/08/arg-telnet-client-is-disabled-by.html' title='Arg! the telnet client is disabled by default in Vista'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=5601217146966646150' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/5601217146966646150'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/5601217146966646150'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-3026923746199923135</id><published>2008-08-25T15:17:00.003-06:00</published><updated>2008-08-25T15:31:11.173-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='NHibernate'/><category scheme='http://www.blogger.com/atom/ns#' term='Out of Curiosity'/><title type='text'>Adding an NHibernate collection to your QuickWatch initializes it</title><summary type='text'>I spent most of the day trying to improve performance on an application. We use NHibernate 2.0 and try to lazy load most of the collections. 
I found these two links very useful for troubleshooting my performance issue:
http://djeeg.blogspot.com/2006/08/nhibernateutilisinitialized.html
and the NHibernate reference:
http://www.hibernate.org/hib_docs/nhibernate/html/performance.html

The curious </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/08/adding-nhibernate-collection-to-your.html' title='Adding an NHibernate collection to your QuickWatch initializes it'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=3026923746199923135' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/3026923746199923135'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/3026923746199923135'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-1855408082220684004</id><published>2008-08-06T12:35:00.003-06:00</published><updated>2008-08-06T12:44:17.321-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SQL Server stuff'/><category scheme='http://www.blogger.com/atom/ns#' term='Merge Replication'/><title type='text'>This merge replication error: The merge process could not connect to the Publisher 'Server:database' is so misleading</title><summary type='text'>We have a merge topology in place with pull subscriptions, this is the merge agent runs at the subscribers.
One of our subscriptions in had the error that the merge process couldn't find the server. The server was there and the ping was fine, also the Replication Monitor was able to register the error with the x mark.

The details of the ertor are as follows:

Command attempted:

{call </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/08/merge-replication-error-merge-process.html' title='This merge replication error: The merge process could not connect to the Publisher &apos;Server:database&apos; is so misleading'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=1855408082220684004' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/1855408082220684004'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/1855408082220684004'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-1657470372743965741</id><published>2008-07-31T15:47:00.005-06:00</published><updated>2008-07-31T16:39:19.324-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Reporting Services'/><category scheme='http://www.blogger.com/atom/ns#' term='SQL Server stuff'/><title type='text'>My wish list for SSRS 2005 and 2008</title><summary type='text'>Right now I'm swamped making reports in SSRS 2005. Even though that might be considered a junior's task I found it interesting. Last time I created report templates was 10 years ago with Quick Reports and VB 6 in the late 1990s :-p

My team recommended SSRS over Crystal Reports and VTO mainly because we have had a previous bad experience with word templates for report generation and really liked </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/07/my-wish-list-for-ssrs-2005-and-2008.html' title='My wish list for SSRS 2005 and 2008'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=1657470372743965741' title='1 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/1657470372743965741'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/1657470372743965741'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-3002793835463920542</id><published>2008-07-08T23:11:00.003-06:00</published><updated>2008-07-08T23:17:15.136-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SQL Server stuff'/><category scheme='http://www.blogger.com/atom/ns#' term='Merge Replication'/><title type='text'>Lets rectify this error (was Compressed snapshot check makes it fail on one subscriber)</title><summary type='text'>
I published a post with the wrong title. It was Compressed snapshot check makes it fail on one subscriber

However the file dynsnapvalidation.tok appears inside the partitioned snapshot whether you select snapshot compression or not. This .tok file shows up if you create data partitions per parameterized filter.</summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/07/lets-rectify-this-error-was-compressed.html' title='Lets rectify this error (was Compressed snapshot check makes it fail on one subscriber)'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=3002793835463920542' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/3002793835463920542'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/3002793835463920542'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-1929842235106676788</id><published>2008-06-19T12:14:00.002-06:00</published><updated>2008-06-19T12:16:36.890-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='.NET'/><category scheme='http://www.blogger.com/atom/ns#' term='Out of Curiosity'/><title type='text'>If you call your .NET application from a batch file...</title><summary type='text'>If you deploy your .NET applications with a batch file, be aware that the way you call your .NET application might affect how it behaves.

The facts are as follows (for our application anyways):

when the application is called using the following line in the batch file:

start C:\Progra~1\ApplicationFolder\Application.exe

the application fails

if you call the application using the windows </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/06/if-you-call-your-net-application-from.html' title='If you call your .NET application from a batch file...'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=1929842235106676788' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/1929842235106676788'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/1929842235106676788'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-3425175830301530743</id><published>2008-06-19T11:03:00.006-06:00</published><updated>2008-06-19T14:52:09.528-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='.NET'/><title type='text'>how to determine the assembly evidence at runtime</title><summary type='text'>I ran into a problem the other day, one of the .NET applications we had deployed started crashing on some screens for no apparent reason. The application worked fine in the development environment and when called from the C drive in the test machine.
We tested for binding problems using the SDK tool fuslogvw.exe, but didn't see any binding errors. The other SDK tool we tried was the .NET </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/06/how-to-determine-assembly-evidence-at.html' title='how to determine the assembly evidence at runtime'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=3425175830301530743' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/3425175830301530743'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/3425175830301530743'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-5568252947122885232</id><published>2008-06-11T07:49:00.011-06:00</published><updated>2008-06-11T20:13:38.693-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='.NET 2.0'/><title type='text'>Encoding troubles, wait, your ANSI file is not the same as my ANSI file</title><summary type='text'>Last week we made a utility for the release team to convert all the t-sql script files from any encoding to ANSI. Now we convert any encoding to Unicode, but the original request was to use ANSI encoding.
The .NET code we used basically opens with a StreamReader that detects encoding, opens a StreamWriter to a new file with Encoding.Default (now Encoding.Unicode) and writes the content read by </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/06/encoding-troubles-wait-your-ansi-file.html' title='Encoding troubles, wait, your ANSI file is not the same as my ANSI file'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=5568252947122885232' title='1 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/5568252947122885232'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/5568252947122885232'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-2846188975077486013</id><published>2008-06-10T10:22:00.003-06:00</published><updated>2008-06-10T10:27:26.971-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Merge Replication'/><title type='text'>Compressed snapshot check makes it fail on one subscriber</title><summary type='text'>As this blog has my personal bread crumbs I thought I would better record this.

We have problems with our merge replication topology (SQL Server 2005 9.0.3228 Publisher and Dist and SQLE 9.0.3228 as Subscribers, pull subscriptions) the other day as we switched to compressed snapshots. I posted the problem in the forum and searched the books about it without luck...

Here's the problem

 We </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/06/compressed-snapshot-check-makes-it-fail.html' title='Compressed snapshot check makes it fail on one subscriber'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=2846188975077486013' title='4 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/2846188975077486013'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/2846188975077486013'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-55033962659309377</id><published>2008-06-02T08:57:00.003-06:00</published><updated>2008-06-02T09:03:13.278-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web services'/><category scheme='http://www.blogger.com/atom/ns#' term='interop'/><title type='text'>Web Services Contract First doesn't guarantee Interop always</title><summary type='text'>I found this very good article that answered part of the questions I had on my previous post.
The part that is enlightening regarding WSCF as how despite that it might be less productive than Code-first, might offer better Interop in the long run is:

What? Code-first is interoperable?  Well sure! You generate schema from code, proxies consume schema and generate a representation of the schema </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/06/web-services-contract-first-doesnt.html' title='Web Services Contract First doesn&apos;t guarantee Interop always'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=55033962659309377' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/55033962659309377'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/55033962659309377'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-443182746663156506</id><published>2008-05-31T10:18:00.003-06:00</published><updated>2008-05-31T10:47:00.295-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web services'/><title type='text'>Web Services Contract First???</title><summary type='text'>I know we .NET developers have been spoiled for a while.

We go on VS2005 and create a new web site project, select the type of project as web service and voila, we land on a page where we can start typing new methods for this class and mark them as web methods with a single annotation. VS2005 does all the plumbing for us creating the wsdl and even publishing the web service for us with another </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/05/web-services-contract-first.html' title='Web Services Contract First???'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=443182746663156506' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/443182746663156506'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/443182746663156506'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-5014094962254453362</id><published>2008-05-14T22:26:00.003-06:00</published><updated>2008-05-14T22:47:21.139-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='fooling around'/><title type='text'>To be or not to be, do you know the answer?</title><summary type='text'>It's 0xFF  on a Byte.

0x2B | ~0x2B = 0xFF</summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/05/to-be-or-not-to-be-do-you-know-answer.html' title='To be or not to be, do you know the answer?'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=5014094962254453362' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/5014094962254453362'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/5014094962254453362'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-8380672079330558240</id><published>2008-04-23T18:37:00.006-06:00</published><updated>2008-04-23T19:26:20.595-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Privacy concerns'/><title type='text'>Getting spam from Gmail</title><summary type='text'>Today I received a phishing email from an account in Google.

What is sad is that Google wants to protect its clients so badly that there is no trace of the client's IP on the email headers. All you see is the Google's IP.

This, imho, is not right. I want to see the sender, if the sender is so concerned about his/her IP being exposed, he/she sure will know enough to hide it. This is not Google's</summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/04/getting-spam-from-google.html' title='Getting spam from Gmail'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=8380672079330558240' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/8380672079330558240'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/8380672079330558240'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-737495877312903401</id><published>2008-04-22T14:59:00.003-06:00</published><updated>2008-04-22T15:04:42.282-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='basic windows'/><title type='text'>On which AD group are you?</title><summary type='text'>On Windows based enterprise with Active Directory it is very usual to use AD groups to reinforce access lists/authentication within enterprise applications/services/databases and mashups.

If you're lost at why you cannot access some application to take a look at, and that application uses integrated security, you're better off knowing which AD group your username is associated with...

On the OS</summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/04/on-which-ad-group-are-you.html' title='On which AD group are you?'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=737495877312903401' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/737495877312903401'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/737495877312903401'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-5852540724384873975</id><published>2008-04-14T09:54:00.004-06:00</published><updated>2008-04-14T14:09:08.841-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='fooling around'/><title type='text'>Handy links if you like to compare</title><summary type='text'>VB.NET and C# Comparison

Java (J2SE 5.0) and C# Comparison
       C# vs Ruby Smackdown!log4net vs EL 1.0
SQL Server 2000 vs Oracle 9i
A Comparison of PL/SQL and Transact SQL
and last but not least:
Comparison of SOA Suites 
Note there is an ESB implementation from P&amp;P for BizTalk 2006 R2 that sort of leverage the missing functionality in the product:  ESB Guidance for BizTalk Server 2006 R2

Ok,</summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/04/handy-links-if-you-like-to-compare.html' title='Handy links if you like to compare'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=5852540724384873975' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/5852540724384873975'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/5852540724384873975'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-3594414802035511428</id><published>2008-04-09T12:42:00.002-06:00</published><updated>2008-04-09T13:00:42.466-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SQL Server stuff'/><title type='text'>Tips and tricks for applying SQL Server 2005 hotfixes</title><summary type='text'>Tips and tricks:
You can install any hotfix in silent mode passing the parameter /quiet to the executable in the command prompt or in a batch file. This is extremely helpful if you want to push the hotfix installation with a third party tool and without the wizard interface
The /? parameter will give you the rest of the options for installing the hotfix. A very useful option is /allinstancesYou </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/04/tips-and-tricks-for-applying-sql-server.html' title='Tips and tricks for applying SQL Server 2005 hotfixes'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=3594414802035511428' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/3594414802035511428'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/3594414802035511428'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-1632611420786105647</id><published>2008-03-12T12:53:00.006-06:00</published><updated>2008-04-09T11:52:52.329-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='.NET Windows Forms'/><title type='text'>The ListView control in System.Windows.Forms 2.0 has a bug</title><summary type='text'>Oh my, the end users are going to get really entertained with this bug.

I'm trying to present images as icons on a list view and the end user should drag and drop the image to the desired location inside the list view to have their list ordered. Unfortunately no matter to which position you drag and drop the image, the image is always placed at the end.
I found a forum post about this with no </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/03/listview-control-in-systemwindowsforms.html' title='The ListView control in System.Windows.Forms 2.0 has a bug'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=1632611420786105647' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/1632611420786105647'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/1632611420786105647'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-8448573210810811837</id><published>2008-03-03T08:32:00.003-07:00</published><updated>2008-03-03T08:45:28.005-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='fooling around'/><title type='text'>Monday morning random rambling...</title><summary type='text'>Now that caffeine is taking effect: I attended the Heroes Happen Here event in Toronto last week. The event was fun in general, lots of marketing going on so the developers get really biased, towards Microsoft technologies, of course...
Not that this is necessarily a bad thing, as long as you keep your mind open to what's going on on other development niches and keep the constructive criticism.
I</summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/03/monday-morning-random-rambling.html' title='Monday morning random rambling...'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=8448573210810811837' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/8448573210810811837'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/8448573210810811837'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-142194177183398907</id><published>2008-02-20T11:47:00.004-07:00</published><updated>2008-02-21T08:02:00.724-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SQL Server stuff'/><category scheme='http://www.blogger.com/atom/ns#' term='Merge Replication'/><title type='text'>The fix for batch deletions at Publisher when use_partition_groups is set to false In Merge Replication is indeed there!!!</title><summary type='text'>Yay!

The fix is in there. Please see previous post for the original bug description. We had problems when not using partition groups on our merge replication topology, whenever there were batch deletions caused by filtering those rows were deleted at the publisher during the next replication.

The faulty stored procedure was sp_MSdelsubrowsbatch


The faulty line of code, believe it or not, a </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/02/fix-for-batch-deletions-at-publisher.html' title='The fix for batch deletions at Publisher when use_partition_groups is set to false In Merge Replication is indeed there!!!'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=142194177183398907' title='3 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/142194177183398907'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/142194177183398907'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-1913087546128184816</id><published>2008-02-20T11:10:00.004-07:00</published><updated>2008-02-20T11:17:49.465-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SQL Server stuff'/><category scheme='http://www.blogger.com/atom/ns#' term='Merge Replication'/><title type='text'>Cumulative Update Number 6 for SQL Server 2005 SP2 is out!!!</title><summary type='text'>Hi DBAs and Database Developers out there,
Finally the long awaited CU#6 was released on Feb 18th near mid night.

946608  Cumulative update package 6 for SQL Server 2005 Service Pack 2
http://support.microsoft.com/default.aspx?scid=kb;EN-US;946608

I'm currently testing our merge replication issues with this CU.

Even though the bug described in the DevX article is not in the KB article list, we</summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/02/cumulative-update-number-6-for-sql.html' title='Cumulative Update Number 6 for SQL Server 2005 SP2 is out!!!'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=1913087546128184816' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/1913087546128184816'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/1913087546128184816'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-3860323463089553154</id><published>2008-02-14T12:10:00.005-07:00</published><updated>2008-02-14T12:43:19.255-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SQL Server stuff'/><category scheme='http://www.blogger.com/atom/ns#' term='Merge Replication'/><title type='text'>Identity Range not working for Merge Replication in SQL Server 2005</title><summary type='text'>Back in Sept 2007 I blogged about the problem we were having with the identity range in merge replication:@@identity not working after SQL Server 2005 upgrade The problem continued until today, this post is to explain what we figured out.

The error message that describes this problem reads as follows:

[548] The insert failed. It conflicted with an identity range check constraint in database '</summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/02/identity-range-not-working-for-merge.html' title='Identity Range not working for Merge Replication in SQL Server 2005'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=3860323463089553154' title='6 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/3860323463089553154'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/3860323463089553154'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-3291594250445229660</id><published>2008-02-04T19:45:00.000-07:00</published><updated>2008-02-04T20:02:23.230-07:00</updated><title type='text'>Yay!!!! The team is on TechNet Innovation Awards 2008</title><summary type='text'>Hi Developer that wanders the internet searching for the solution to your bug. Take a brief moment and vote for us, bunch of developers who also wander the internet to search solutions for our bugs and  blog about them to help others :)

Microsoft Canada and TechNet Innovation Code Awards


We'll be good and post more on our blog, interesting, good stuff :-p
Kidding, let the code prevail!

Oh, </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/02/yay-team-is-on-technet-innovation.html' title='Yay!!!! The team is on TechNet Innovation Awards 2008'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=3291594250445229660' title='1 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/3291594250445229660'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/3291594250445229660'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-988736960137291819</id><published>2008-01-17T12:21:00.000-07:00</published><updated>2008-01-17T12:49:02.416-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SQL Server stuff'/><title type='text'>Merge replication issues in SQL Server 2005 and comments on MS employee's blog</title><summary type='text'>Hi all,
As I mentioned in my previous post,  i would provide details of the data loss scenarios in Merge Replication topologies with SQL Server 2005. The details were published in this addendum to the original DevX article:

UPDATED SQL Server 2005 Bug Alert: Data Loss in Merge Replication

the article is basically two repros to illustrate the data loss when the partition groups are not use in </summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2008/01/merge-replication-issues-in-sql-server.html' title='Merge replication issues in SQL Server 2005 and comments on MS employee&apos;s blog'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=988736960137291819' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/988736960137291819'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/988736960137291819'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-14212809.post-5731335850611692152</id><published>2007-12-19T07:21:00.000-07:00</published><updated>2007-12-20T14:38:04.694-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SQL Server stuff'/><category scheme='http://www.blogger.com/atom/ns#' term='Merge Replication'/><title type='text'>Merge Replication parameterized row filtering, beware of the optimizations</title><summary type='text'>I haven't blogged in a while, mostly due to my workload that has sky rocketed.
My most recent challenge is with SQL Server 2005 Merge Replication.

We have had quite a few undesirable effects when we upgraded our subscribers from ole good MSDE to SQL Server Express.
The side effects led to data loss and emergency fixes, in a really chaotic way. This data loss didn't happen with MSDE.

The article</summary><link rel='alternate' type='text/html' href='http://theniceweb.com/2007/12/merge-replication-parameterized-row.html' title='Merge Replication parameterized row filtering, beware of the optimizations'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14212809&amp;postID=5731335850611692152' title='0 Comments'/><link rel='replies' type='application/atom+xml' href='http://theniceweb.com/LizisBlog/atom.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/5731335850611692152'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14212809/posts/default/5731335850611692152'/><author><name>Lizet Pena de Sola</name><uri>http://www.blogger.com/profile/00040573571492625636</uri><email>noreply@blogger.com</email></author></entry></feed>