Tuesday, November 9, 2010

HOW TO MAXIMIZE YOUR LAN SPEED

Hello, Are you thinking that your LAN speed is slow, if so than you should read this to attain maximum speed from your LAN

1. Right click on My Computer and click properties


2. Now under Hardware tab click on Device Manager


3. Now Double click on the network adopter that you are using.




4. Now under Advance tab, click on Speed & Duplex ( If there is no Speed & duplex, than there could be Media Type or may be Link Speed & Duplex) just click on it.


5. Now from the drop down menu, select 100 Mb full or 100 Mbps Full Duplex

6. Click on OK

Now you can fully utilize your LAN

REMEMBER: In order to achieve full speed, the computer from which you are downloading should also have been setup to 100 Mb full Duplex

By this way you can also limit your LAN speed, just select Half duplex or whatever limit you want

HOW TO RUN MULTIPLE INSTANCE OF MSN MESSENGER WITHOUT USING ANY SOFTWARE

Hello Today I am going to show you how to make your MSN messenger 2009, MULTI without using any softwares..


1. Click on run and type regedit and press OK


A window will open like this


2. Now Expand HKEY_LOCAL_MACHINE, than expand SOFTWARE, than expand Microsoft, than expand Windows Live, and than click on Messenger

3. Now on the right side, right click and than New, and than DWORD Value


4. Name it MultipleInstances


5. Double click on it, and Set its value to 1 and click on ok


6. Close registry Editor

:) thats all you should now be able to run multiple instance of msn messenger

Saturday, November 6, 2010

T SQL: UNABLE TO USE COLUMN ALIAS IN WHERE CLAUSE

Since I started working over T SQL I have faces many issues in query and resolved them by walking through blogs, however; one thing that I always thought about, was the reasons behind those issues.

One of those issues is that we can't use column alias in where clause, for instance:

SELECT SUM(CoustmerId) AS OrderCount ... WHERE OrderCount > 2000

We can't do this because in the execution order of an SQL statement SELECT clause executes after WHERE clause.

I thought that was the issue with T SQL compiler, however; later I figured out that the issue is not because of T SQL compiler but because of my lack of knowledge.

I hope this post will help people. Have a nice day.

SQL or SEQUEL

Many database professionals or even other people who have any concern with databases pronounce SQL as sequel, although the correct pronunciation of the language is S-Q-L ("ess kyoo ell"). According to my guess there are both historical reasons and linguistic resons behind it.

We need to look back into the history to know reasone. In the 1970s IBM developed a language called SEQUEL, which was an acronym for Structured English Query Language. This language was designed inorder to manipulate data stored in a database system known as System R. Later on, the acronym SEQUEL was shortened to SQL because of a trademark dispute.

In 1986 ANSI adopted SQL as a standard, and in 1987 ISO did so. ANSI declared that the official pronunciation of the language is "ess kyoo ell," but it seems that this fact is not common knowledge.
.
As far as linguistic reason is concern, the sequel can be pronunced more fluently, mainly for English speakers. I have to say that I often use it myself for this reason.

You can sometimes guess which pronunciation people use by inspecting their writings. Someone writing "an SQL Server" probably uses the correct pronunciation, while someone writing "a SQL Server" probably uses the incorrect one.

So that was the stroy behind SQL and SEQUEL.

Thursday, November 4, 2010

InfoPath: ‘The following URL is not valid: http://servername:portnumber/sites/sitename’ error


When you are trying to publish InfoPath form to SharePoint’s site and the above error is driving you nuts because you have confirmed that that the site is being opening from browser and the URL you are providing is valid then what the is happening, the site is up as well then where you made mistake, where things went wrong.
These are the same questions; this is the same feeling I had when I was facing this issue. After searching over internet I figured out that this is happening because I dint created site at the root level.
Which would be at this http://servrname:port#/ location.
The resolution of this issue is to create root site means creating site at this http://servrname:port#/ level.
Try it and get your InfoPath published. Have a nice day J.