Hot Add Memory
One of the smaller improvements made to SQL Server 2005 was the ability of SQL Server to utilize memory added while SQL Server was online and running. SQL Server before 2005 supported dynamic memory but if you needed to add memory to a server after you had started SQL Server, you couldn’t since SQL Server only recognized the memory that was present during start up. SQL Server 2005 added support for Hot Add Memory. While this is a great concept, I probably will have a hard time finding more than 2 people in the SQL Server world how have actually utilize this feature. I bet I could a few dozen who needed this feature but didn’t know about it or who knew about the feature but didn’t have their server configure to utilize Hot Add Memory. I hope this little blog helps a few database administrators understand this concept and how it may help them in the future.
So what is Hot Add Memory?
What Hot Add Memory basically means that a Windows administrator can crack open the case of a server, add new memory, and then close the server up and Windows and SQL Server will recognize that additional memory and utilize it without having to be bounced. This allows for the addition of extra memory at a later date without having to schedule server or SQL Server downtime. The ability of having additional memory added without downtime may actually serve a few of us with our uptime requirements or even allow us to put a server into place before we actually have that additional memory we figured out at a later date that we really needed for new environment.
So how do you configure your server to utilize Hot Add Memory?
As stated above, Hot Add Memory requires either Windows 2003 or later Enterprise or Data Center Edition. Hot Add Memory is available for both 64-bit and 32-bit SQL server. Hot Add Memory is a server feature that some of the server have, older servers may not the ability to add hot memory since the server itself must have the configuration and feature set added to the server, and requires either Windows 2003 (or 2008) Enterprise or Data Center edition.
There are a few SQL Server related configurations that must be in place before SQL Server can actually make use of Hot Add Memory. If you are on a 32-bit version, you must have AWE enabled, even if you do not have more than 4GB of memory. You cannot make use of Hot Add Memory without AWE. Another item which will keep most database administrators from using Hot Add Memory is that you must have the –h startup option in place before using Hot Add Memory on a 32-bit version. This startup parameter reserves additional virtual address space for the Hot Add Memory metadata when using 32-bit AWE and since it is a startup parameter, you must have set –h before starting SQL Server. While you could just set this parameter on all your servers and be done with it, the parameter comes with a price. The –h startup parameter consumes 500 MB of virtual address space. Remember VAS is limited to the first 2GB of memory (3GB of memory if you are using the /3GB switch) on a 32-bit installation. This means that 500 MB of the 2GB is being used for Hot Add Memory metadata. Just having this parameter set may cause the need to add additional memory. Be careful when setting this parameter and only do it for servers you know will require additional memory but the memory is still on order and you just need to put what you have in place before it comes in. I would also remove the parameter as soon as I added the new memory so that on the new reboot the 500MB of memory can be recaptured for SQL Server to utilize.
One good thing, if your server (not SQL Server) is configured to use Hot Add Memory, you no longer have to use the /PAE switch in the boot.ini. No, the 500MB will not be automatically consumed as the –h startup parameter is a SQL Server parameter, not a Windows setting.
Note: If for some reason you remove memory from a server - I can’t think of a single time I would allow this to happen to any of my servers - you still have to restart everything. There is no Hot Remove Memory feature.
Summary
This was just a small posting about a feature of SQL Server 2005 and 2008 that most of us do not know about. I know it will not be a heavily used feature, but when you need it, it will be great to know about Hot Add Memory.
Friday, November 21, 2008
Thursday, September 18, 2008
Tips for Torrent Client Config
http://www.clixsense.com/?2592760
Torrent Client Configuration
In order to apply these tips you need to know your maximum up- and download speed. You can test your bandwidth over here (stop all download activity while testing). Also make sure that you applied the tips provided in our previous posts.
Note that there’s a huge difference between kb/s(kilobits/second) and kB/s (kilobytes/second). To be precise, kB/s = kb/s divided by 8. In this tutorial we use
kB/s (like most torrent clients do). This means that you might need to calculate your max speed in kB/s yourself if the speedtest only gives you the results in kb\s (so divide by 8 then).
Settings 1-4 can be found in the options, settings or preference tab of most torrent clients.
1. Maximum upload speed
Probably the most important setting there is. Your connection is (sort of) like a pipeline, if you use you maximum upload speed there’s not enough space left for the
files you are downloading. So you have to cap your upload speed. Use the following formula to determine your optimal upload speed…
80% of your maximum upload speed
So, if your maximum upload speed is 40 kB/s, the optimal upload rate is 32kB/s
But keep seeding!
2. Maximum download speed
Although setting your maximum download speed to unlimited may sound interesting, in reality it will only hurt your connection. If you still want to be able to browse
properly, set your maximum download speed to: 95% of your maximum download speed
so if your maximum download speed is 400 kB/s, the optimal download speed is 380kB/s
3. Maximum connected peers per torrent
Yet another setting that you don’t want to max out.I experimented quite a lot with the max connected peers settings and came to the conclusion that both high and low
number hurt the download speed of a torrent. The following setting worked best for me.upload speed * 1.3 so, if your maximum upload speed is 40 kB/s, the optimal
amount of connected peers per torrent is 40 * 1.3 = 52
I didn’t noticed a difference for fast or slow connections here.
4. Maximum upload slots
1 + (upload speed / 6)
So, if your maximum upload speed is 30 kB/s, the optimal number of upload slots is
1 + (30 / 6) = 6
5. More tips
A. Seed.
Downloading speeds will be sub-optimal for everyone unless everyone plays their part and seeds. Private tracker sites are a great example of how the overall speed of the swarm increases when everyone is seeding and downloading in equal measure. So, play your part in seeding and tell others to as well.
B. Be connectable.
Make sure you’re not “firewalled” by opening up your incoming ports or by enabling UPnP in your router, otherwise you’ll be leaving bandwidth on the table.
C. Select the right torrents.
Your download will be faster if you choose to download a torrent where there is a good balance of seeds and peers. For instance, Vuze ranks its search results according to the number of seeds and peers to make this easier.
D. Be realistic.
Check the swarm average and if you’re already above average, then you just need to be patient. If you’re below average, go back and check some of these other things I’ve
mentioned.
Sunday, September 14, 2008
The History of the Middle Finger
Well, now......here' s something I never knew before, and now that I know it, I feel compelled to send it on to my more intelligent friends in the hope that they, too, will feel edified. Isn't history more fun when you know something about it?
Before the Battle of Agincourt in 1415, the French, anticipating victory over the English, proposed to cut off the middle finger of all captured English soldiers. Without the middle finger it would be impossible to draw the renowned English longbow and therefore they would be incapable of fighting in the future. This famous English longbow was made of the native English Yew tree, and the act of drawing the longbow was known as "plucking the yew" (or "pluck yew").
Much to the bewilderment of the French, the English won a major upset and began mocking the French by waving their middle fingers at the defeated French, saying, See, we can still pluck yew! Since 'pluck yew' is rather difficult to say, the difficult consonant cluster at the beginning has gradually changed to a labiodentals fricative F', and thus the words often used in conjunction with the one-finger-salute! It is also because of the pheasant feathers on the arrows used with the longbow that the symbolic gesture is known as "giving the bird."
IT IS STILL AN APPROPRIATE SALUTE TO THE FRENCH TODAY!
And yew thought yew knew every plucking thing.
Sunday, August 24, 2008
List of Port numbers
|
List of frequently seen TCP and UDP ports and what they mean. The goal of this port table is to point to further resources for more information.
0 | |
1 | tcpmux |
3 | |
4 | |
5 | rje |
7 | echo |
9 | discard |
11 | systat |
13 | daytime |
15 | netstat |
17 | qotd |
18 | send/rwp |
19 | chargen |
20 | ftp-data |
21 | ftp |
22 | ssh, pcAnywhere |
23 | Telnet |
25 | SMTP |
27 | ETRN |
29 | msg-icp |
31 | msg-auth |
33 | dsp |
37 | time |
38 | RAP |
39 | rlp |
40 | |
41 | |
42 | nameserv, WINS |
43 | whois, nickname |
49 | TACACS, Login Host Protocol |
50 | RMCP, re-mail-ck |
53 | DNS |
57 | MTP |
59 | NFILE |
63 | whois++ |
66 | sql*net |
67 | bootps |
68 | bootpd/dhcp |
69 | Trivial File Transfer Protocol (tftp) |
70 | Gopher |
79 | finger |
80 | www-http |
87 | |
88 | Kerberos, WWW |
95 | supdup |
96 | DIXIE |
98 | linuxconf |
101 | HOSTNAME |
102 | ISO, X.400, ITOT |
105 | cso |
106 | poppassd |
109 | POP2 |
110 | POP3 |
111 | Sun RPC Portmapper |
113 | identd/auth |
115 | sftp |
116 | |
117 | uucp |
118 | |
119 | NNTP |
120 | CFDP |
123 | NTP |
124 | SecureID |
129 | PWDGEN |
133 | statsrv |
135 | loc-srv/epmap |
137 | netbios-ns |
138 | netbios-dgm (UDP) |
139 | NetBIOS |
143 | IMAP |
144 | NewS |
150 | |
152 | BFTP |
153 | SGMP |
156 | |
161 | SNMP |
175 | vmnet |
177 | XDMCP |
178 | NextStep Window Server |
179 | BGP |
180 | SLmail admin |
199 | smux |
210 | Z39.50 |
213 | |
218 | MPP |
220 | IMAP3 |
256 | |
257 | |
258 | |
259 | ESRO |
264 | FW1_topo |
311 | Apple WebAdmin |
350 | MATIP type A |
351 | MATIP type B |
360 | |
363 | RSVP tunnel |
366 | ODMR (On-Demand Mail Relay) |
371 | |
387 | AURP (AppleTalk Update-Based Routing Protocol) |
389 | LDAP |
407 | Timbuktu |
427 | |
434 | Mobile IP |
443 | ssl |
444 | snpp, Simple Network Paging Protocol |
445 | SMB |
458 | QuickTime TV/Conferencing |
468 | Photuris |
475 | |
500 | ISAKMP, pluto |
511 | |
512 | biff, rexec |
513 | who, rlogin |
514 | syslog, rsh |
515 | lp, lpr, line printer |
517 | talk |
520 | RIP (Routing Information Protocol) |
521 | RIPng |
522 | ULS |
531 | IRC |
543 | KLogin, AppleShare over IP |
545 | QuickTime |
548 | AFP |
554 | Real Time Streaming Protocol |
555 | phAse Zero |
563 | NNTP over SSL |
575 | VEMMI |
581 | Bundle Discovery Protocol |
593 | MS-RPC |
608 | SIFT/UFT |
626 | Apple ASIA |
631 | IPP (Internet Printing Protocol) |
635 | mountd |
636 | sldap |
642 | EMSD |
648 | RRP (NSI Registry Registrar Protocol) |
655 | tinc |
660 | Apple MacOS Server Admin |
666 | Doom |
674 | ACAP |
687 | AppleShare IP Registry |
700 | buddyphone |
705 | AgentX for SNMP |
901 | swat, realsecure |
993 | s-imap |
995 | s-pop |
999 | |
1024 | |
1025 | |
1050 | |
1062 | Veracity |
1080 | SOCKS |
1085 | WebObjects |
1100 | |
1105 | |
1114 | |
1227 | DNS2Go |
1234 | |
1243 | SubSeven |
1338 | Millennium Worm |
1352 | Lotus Notes |
1381 | Apple Network License Manager |
1417 | Timbuktu |
1418 | Timbuktu |
1419 | Timbuktu |
1420 | |
1433 | Microsoft SQL Server |
1434 | Microsoft SQL Monitor |
1477 | |
1478 | |
1490 | |
1494 | Citrix ICA Protocol |
1498 | |
1500 | |
1503 | T.120 |
1521 | Oracle SQL |
1522 | |
1524 | |
1525 | prospero |
1526 | prospero |
1527 | tlisrv |
1529 | |
1547 | |
1604 | Citrix ICA, MS Terminal Server |
1645 | RADIUS Authentication |
1646 | RADIUS Accounting |
1680 | Carbon Copy |
1701 | L2TP/LSF |
1717 | Convoy |
1720 | H.323/Q.931 |
1723 | PPTP control port |
1731 | |
1755 | Windows Media .asf |
1758 | TFTP multicast |
1761 | |
1762 | |
1808 | |
1812 | RADIUS server |
1813 | RADIUS accounting |
1818 | ETFTP |
1968 | |
1973 | DLSw DCAP/DRAP |
1975 | |
1978 | |
1979 | |
1985 | HSRP |
1999 | Cisco AUTH |
2000 | |
2001 | glimpse |
2005 | |
2010 | |
2023 | |
2048 | |
2049 | NFS |
2064 | distributed.net |
2065 | DLSw |
2066 | DLSw |
2080 | |
2106 | MZAP |
2140 | DeepThroat |
2301 | Compaq Insight Management Web Agents |
2327 | Netscape Conference |
2336 | Apple UG Control |
2345 | |
2427 | MGCP gateway |
2504 | WLBS |
2535 | MADCAP |
2543 | sip |
2565 | |
2592 | netrek |
2727 | MGCP call agent |
2766 | |
2628 | DICT |
2998 | ISS Real Secure Console Service Port |
3000 | Firstclass |
3001 | |
3031 | Apple AgentVU |
3052 | |
3128 | squid |
3130 | ICP |
3150 | DeepThroat |
3264 | ccmail |
3283 | Apple NetAssitant |
3288 | COPS |
3305 | ODETTE |
3306 | mySQL |
3352 | |
3389 | RDP Protocol (Terminal Server) |
3520 | |
3521 | netrek |
3879 | |
4000 | icq, command-n-conquer |
4045 | |
4144 | |
4242 | |
4321 | rwhois |
4333 | mSQL |
4444 | |
47017 | |
4827 | HTCP |
5000 | |
5001 | |
5002 | |
5004 | RTP |
5005 | RTP |
5010 | Yahoo! Messenger |
5050 | |
5060 | SIP |
5135 | |
5150 | |
5190 | AIM |
5222 | |
5353 | |
5400 | |
5500 | securid |
5501 | securidprop |
5300 | |
5423 | Apple VirtualUser |
5555 | |
5556 | |
5631 | PCAnywhere data |
5632 | PCAnywhere |
5678 | |
5800 | VNC |
5801 | VNC |
5900 | VNC |
5901 | VNC |
5843 | |
6000 | X Windows |
6112 | BattleNet |
6050 | |
6499 | |
6500 | |
6502 | Netscape Conference |
6547 | |
6548 | |
6549 | |
6666 | |
6667 | IRC |
6670 | VocalTec Internet Phone, DeepThroat |
6699 | napster |
6776 | Sub7 |
6968 | |
6969 | |
6970 | RTP |
6971 | |
7000 | |
7007 | MSBD, Windows Media encoder |
7070 | RealServer/QuickTime |
7161 | |
7323 | |
7777 | |
7778 | Unreal |
7640 | |
7648 | CU-SeeMe |
7649 | CU-SeeMe |
7654 | |
8000 | |
8002 | |
8010 | WinGate 2.1 |
8080 | HTTP |
8100 | |
8181 | HTTP |
8383 | IMail WWW |
8765 | |
8875 | napster |
8888 | napster |
8890 | |
9000 | |
9090 | |
9200 | |
9704 | |
9669 | |
9876 | |
9989 | |
10008 | cheese worm |
10752 | |
12345 | |
11371 | PGP 5 Keyserver |
12346 | |
13000 | |
13223 | PowWow |
13224 | PowWow |
14000 | |
14237 | Palm |
14238 | Palm |
14690 | |
16969 | |
18888 | LiquidAudio |
21157 | Activision |
22555 | |
22703 | |
22793 | |
23213 | PowWow |
23214 | PowWow |
23456 | EvilFTP |
26000 | Quake |
27000 | |
27001 | QuakeWorld |
27010 | Half-Life |
27015 | Half-Life |
27374 | |
27444 | |
27665 | |
27910 | |
27960 | QuakeIII |
28000 | |
28001 | |
28002 | |
28003 | |
28004 | |
28005 | |
28006 | |
28007 | |
28008 | |
30029 | AOL Admin |
30100 | |
30101 | |
30102 | |
30103 | |
30303 | |
30464 | |
31335 | |
31337 | Back Orifice |
32000 | |
32771 | |
32777 | rpc.walld |
34555 | |
40193 | Novell |
41524 | arcserve discovery |
45000 | Cisco NetRanger postofficed |
50505 | |
52901 | |
54321 | |
61000 | |
65301 | |
Multicast | hidden |
ICMP Type | hidden |
9998 | |
32773 | rpc.ttdbserverd |
32776 | rpc.spray |
32779 | rpc.cmsd |
38036 | timestep |
Subscribe to:
Posts (Atom)