gambar hari raya aidilfitri 2008…. tahun ni raya kat kelantan… kota bharu.. rumah che tokmek…

kiri DIAN SHAZANI, kanan HARITH AZAMI…

Mengenali kuantiti asas, unit asas dan simbol yang diguna pakai dalam ‘daily life’ mengikut buku-buku fizik… what are those quantities and symbols? Table below describes 5 kuantiti asas yang perlu diketahui… kira macam perkara wajib la…

 (all info are taken from: tripod.com)

Jadual 1.1 menunjukkan kuantiti asas, unit asas dan simbol bagi unit asasnya:

And in SI units:

 -   1 meter = Jarak yang dilalui oleh cahaya dalam vakum dalam selang masa 1 ÷  299792458 saat

-   1 kilogram = Jisim satu bongkah silinder aloi platinum-iridium yang disimpan di Biro Antarabangsa bagi Berat dan Sukatan di Sevres, Paris.                          

-   1 saat = Masa yang sama dengan 9192631770 kali tempoh sinaran yang  dikeluarkan oleh atom saesium-1.

-   1 kelvin = 1 ÷ 273.16 suhu termodinamik takat tigaan air (takat ais, air dan stim berada dalam keseimbangan pada tekanan tertentu).

-   1 ampere = 1 ampere ialah arus mantap yang mengalir dalam dua konduktor selari yang panjangnya tak terhingga, luas keratan rentas boleh diabaikan dan dipisahkan sejauh 1 meter dalam vakum yang menghasilkan daya sebanyak  2 × 10⁷ newton per meter di antara konduktor-konduktor itu.

Here is some usefull information to take note of regarding “kuantiti asas” atau kuantiti fizik:

1.Ianya ialah kuantiti yg boleh diukur = countable or measurable quantity 

2.Untuk mengukur sesuatu kuantiti fizik, satu saiz piawai yang dikenali sebagai unit digunakan untuk membandingkan saiz-saiz yang berlainan bagi kuantiti fizik yang sama.

3.Contohnya, kilogram (kg) ialah unit untuk jisim. 1 kilogram ialah jisim satu bongkah logam tertentu yang disimpan di Biro Antarabangsa bagi Berat dan Sukatan di Suvres, Paris.

4.Salinan bongkah ini disimpan di Jabatan Berat dan Sukatan setiap negara. Jisim yang lain kemudian dibandingkan dengan jisim piawai ini (kg) untuk menentukan jisimnya.

5.Jika jisim suatu objek adalah 2 kg bermakna jisimnya adalah dua kali jisim bongkah piawai tersebut.

6.Dalam Sistem Antarabangsa (SI), sistem penyukatan yang dipersetujui pada Persidangan Berat dan Ukuran di Paris 1960, lima kuantiti fizik dipersetujui sebagai kuantiti asas.

7.Kuantiti asas ialah kuantiti fizik yang bukan gabungan dua atau lebih kuantiti fizik yang lain.

8. Unit bagi kuantiti asas ini dikenali sebagai unit asas.

Entitled:

Seamless Handover Mobility Schemes over High Speed Wireless
Environment

Abstract:

Rapid technological advance in computer and wireless mobile communication has widened the Internet functionality to be
practically used in daily’s life. This advancement has offered Internet accessibility at anytime and anywhere including high speed
wireless environment such as in high speed trains, fast moving cars etc. However, wireless Quality of Service (QoS) provisioning
in such high speed movement is more difficult and challenging to be tackled than in a fixed-wired environment.

This challenge
has boost development of numerous schemes that has concerned with the needs to provide smooth handoff in such high speed
mobility. This paper discussed several seamless handover protocols that can guarantees and maintain high QoS in high speed
mobile nodes. The paper also focused on one selected protocol that has been identified to have the ability to perform well in high
speed environment. The limitations of the selected protocol have been identified and a prediction technique is proposed to
improve and optimize its performance in high speed environment.

Entitled:

PERFORMANCE STUDY OF QUALITY OF SERVICE ROUTING PROTOCOLS IN MANETS

Abstract:

Recent growth and widespread attention given to mobile communications has led to rapid proliferation in research and development involving mobile wireless networks. The need for easy deployment and self-configured networks makes mobile ad-hoc networks (MANETs) an attractive choice for various applications. However, due to its dynamic nature and imprecise network state information, there are many challenges which need to be addressed including Quality of Service (QoS) routing. Numerous approaches have been proposed including QoS-AODV. It is proposed to enhance one of the existing routing protocols for MANETs namely AODV (Ad-Hoc On-Demand Distance Vector). QoS-AODV adds necessary new fields to cater QoS provisioning requirements. Due to its ease of integration and simplicity, this protocol has been selected for evaluation study. The existing QoS-AODV implementation utilizes minimum bandwidth extension in assuring QoS guarantee. Apart from bandwidth, delay is also a critical parameter with regards to multimedia application which has been garnering rising attention lately.

The first aim of this thesis is to conduct evaluation study on two QoS-AODV approaches. One approach makes use of HELLO messages and another makes use of link-layer feedback. Meanwhile, our highlighted contribution includes the extension of maximum delay field in addition to the existing minimum bandwidth field as part of our enhancement proposal. In order to identify the pros and cons of both methods as well as to test our proposed mechanism, NS-2 Simulator is used to conduct the simulation study. Average Latency, Packet Delivery Ratio (PDR) and Normalized Overhead are the selected evaluation metrics. Our experiments study the effect of number of mobile nodes, mobility and traffic load on different enhancements of AODV protocol. Even though all the simulated protocols are based on AODV, the connectivity maintenance methods as well as the admission control mechanism adopted have the capabilities to shape the performance. Through the simulation study performed, the shortcomings and strengths of the simulated approaches have been identified thus directing to suggestions for future works.

This procedure is developed by:

/*
**Author Rodrigo Acosta
**E-mail racosta@iecisa.com.ar
*/

CREATE PROCEDURE proc_list_ing
@dbname varchar(20)= NULL
AS
SET NOCOUNT ON
IF @dbname IS NULL
BEGIN
PRINT ‘*****************************************’
PRINT ‘**You must enter a Database Name **’
PRINT ‘**to continue. **’
PRINT ‘*****************************************’
PRINT ”
PRINT ‘Available Databases…’
EXEC master..sp_databases
RETURN
END

IF NOT EXISTS (
SELECT name
FROM master..sysdatabases
WHERE name=@dbname
)
BEGIN
PRINT ‘*****************************************’
PRINT ‘**The database does not exists. **’
PRINT ‘**Available databases… **’
PRINT ‘*****************************************’
PRINT ”
EXEC master..sp_databases
RETURN
END

/*
**Gets the path where the db files are located
**and then puts the list in temp tables.
*/
DECLARE @lenght_db varchar(300)
DECLARE @path_db varchar(300)
DECLARE @numero_db int
SET @lenght_db=(
SELECT filename
FROM master..sysfiles
WHERE name=’master’
)
SET @path_db=(
SELECT filename
FROM master..sysfiles
WHERE name=’master’
)
set @lenght_db=LEN (@lenght_db)
set @numero_db=@lenght_db-10
SET @path_db= left(@path_db,@numero_db)

DECLARE @cmd_mdf varchar(300)
DECLARE @cmd_ldf varchar(300)

SET @cmd_mdf=’EXEC master..xp_cmdshell “dir /B ‘+@path_db+’*.mdf”‘
SET @cmd_ldf=’EXEC master..xp_cmdshell “dir /B ‘+@path_db+’*.ldf”‘

CREATE TABLE #datafiles_mdf
(mdf varchar(40))

CREATE TABLE #datafiles_ldf
(ldf varchar(40))

/*MDF’s y LDF’s saved on tables*/
INSERT INTO #datafiles_mdf EXEC (@cmd_mdf)
INSERT INTO #datafiles_ldf EXEC (@cmd_ldf)

———————————————–
/*
**Checks the user tables on the db
*/
DECLARE @select_table varchar(100)
SET @select_table=’SELECT count(name)AS “Users Tables” FROM ‘+@dbname+’..sysobjects where xtype=”u”‘

———————————————–
/*
**Checks the views
*/
DECLARE @select_view varchar(100)
SET @select_view=’SELECT count(name) AS “Views” FROM ‘+@dbname+’..sysobjects where xtype=”v” ‘

———————————————–
/*
**Checks the system tables
*/
DECLARE @select_sistema varchar(100)
SET @select_sistema=’SELECT count(name)AS “system Tables” FROM ‘+@dbname+’..sysobjects where xtype=”s” ‘

———————————————–
/*
**Checks the SP
*/
DECLARE @select_sp varchar(100)
SET @select_sp=’SELECT count(name) AS “Stored Procedures” FROM ‘+@dbname+’..sysobjects where xtype=”p”‘

———————————————–
/*
**Checks the XP
*/
DECLARE @select_xp varchar(100)
SET @select_xp=’SELECT count(name) AS “Extended Procedures” FROM ‘+@dbname+’..sysobjects where xtype=”x”‘

———————————————–
/*
**Checks the user names
*/
DECLARE @select_users varchar(100)
SET @select_users=’SELECT name AS “Users names” FROM ‘+@dbname+’..sysusers where name not like “db_%”‘

—————————————————————–
/*
**Print the result
*/
PRINT ‘List of .mdf files on the path ‘+@path_db
select mdf as ‘Data files’ from #datafiles_mdf
PRINT ‘List of .ldf files on the path ‘+@path_db
select ldf AS ‘Log files’ from #datafiles_ldf
print ‘Quantity of user tables on the database ‘+@dbname
EXEC (@select_table)
print ‘Quantity of system tables on the database ‘+@dbname
EXEC (@select_sistema)
print ‘Quantity of views on the database ‘+@dbname
EXEC (@select_view)
print ‘Quantity of Stored Procedures on the database ‘+@dbname
EXEC (@select_sp)
print ‘Quantity of Extended Procedures on the database ‘+@dbname
EXEC (@select_xp)
PRINT ‘Users on the database ‘+@dbname
EXEC (@select_users)

Usage

To run, simply call it like usp_killusers ‘dbname’. Make sure the @dbname parameter is not the master database.

CREATE PROCEDURE usp_KillUsers @dbname varchar(50) as
SET NOCOUNT ON

DECLARE @strSQL varchar(255)
PRINT ‘Killing Users’
PRINT ‘—————–’

CREATE table #tmpUsers(
spid int,
eid int,
status varchar(30),
loginname varchar(50),
hostname varchar(50),
blk int,
dbname varchar(50),
cmd varchar(30))

INSERT INTO #tmpUsers EXEC SP_WHO

DECLARE LoginCursor CURSOR
READ_ONLY
FOR SELECT spid, dbname FROM #tmpUsers WHERE dbname = @dbname

DECLARE @spid varchar(10)
DECLARE @dbname2 varchar(40)
OPEN LoginCursor

FETCH NEXT FROM LoginCursor INTO @spid, @dbname2
WHILE (@@fetch_status <> -1)
BEGIN
IF (@@fetch_status <> -2)
BEGIN
PRINT ‘Killing ‘ + @spid
SET @strSQL = ‘KILL ‘ + @spid
EXEC (@strSQL)
END
FETCH NEXT FROM LoginCursor INTO @spid, @dbname2
END

CLOSE LoginCursor
DEALLOCATE LoginCursor

DROP table #tmpUsers
go

1. find someone who will listen

sharing experience is one of the best ways to stay sane. try to find someone close or someone you can trust or may be you can join a parent group. do express how you feel!

2. do not be too hard on yourself

do not worry if you are rushing around all the time and your usual standards slip a bit

The usage is simple, you simply plug the USB and it will auto display a windows with the Imation disk manager application. Just double click it, you can create your own partition on the disk, whether you want it to be totally secured, half secured or etc (you can create your own size of protected disk) and of course create your own password.

- Create an Index object.

- Set the Name property.

- Set the IndexedColumns property to the column or columns participating in the index.

- Set the Type property of the Index object to control the attributes of the index created (optional). If not set, a nonclustered index allowing duplicate values is created. For more information about SQL Server index types and limitations on indexes applied to tables.

- Set optional properties, such as FileGroup.

- Get the Table object that references the SQL Server table you want from the Tables collection of a connected Database object.

- Use the BeginAlter method of the Table object to mark the start of changes to the SQL Server table.

- Add the Index object to the Indexes collection of the selected Table object.

- Use the DoAlter method of the Table object to mark the end of changes and create the index on the SQL Server.

Take note that to creates an index on a given table or view.

Only the table or view owner can create indexes on that table. The owner of a table or view can create an index at any time, whether or not there is data in the table. Indexes can be created on tables or views in another database by specifying a qualified database name.

What is the difference between clustered and non-clustered index?

CLUSTERED :

Creates an object where the physical order of rows is the same as the indexed order of the rows, and the bottom (leaf) level of the clustered index contains the actual data rows. A table or view is allowed one clustered index at a time.

A view with a clustered index is called an indexed view. A unique clustered index must be created on a view before any other indexes can be defined on the same view.

Create the clustered index before creating any nonclustered indexes. Existing nonclustered indexes on tables are rebuilt when a clustered index is created.

NONCLUSTERED

Creates an object that specifies the logical ordering of a table. With a nonclustered index, the physical order of the rows is independent of their indexed order. The leaf level of a nonclustered index contains index rows. Each index row contains the nonclustered key value and one or more row locators that point to the row that contains the value. If the table does not have a clustered index, the row locator is the row’s disk address. If the table does have a clustered index, the row locator is the clustered index key for the row.

Each table can have as many as 249 nonclustered indexes (regardless of how they are created: implicitly with PRIMARY KEY and UNIQUE constraints, or explicitly with CREATE INDEX). Each index can provide access to the data in a different sort order.

For indexed views, nonclustered indexes can be created only on a view with a clustered index already defined. Thus, the row locator of a nonclustered index on an indexed view is always the clustered key of the row.

Example index query

This example creates a simple index on the au_id column of the authors table.

SET NOCOUNT OFF
USE pubs
IF EXISTS (SELECT name FROM sysindexes
WHERE name = ‘au_id_ind’)
DROP INDEX authors.au_id_ind
GO
USE pubs
CREATE INDEX au_id_ind
ON authors (au_id)
GO

This example creates a unique clustered index on the employeeID column of the emp_pay table that enforces uniqueness. This index physically orders the data on disk because the CLUSTERED clause is specified.

SET NOCOUNT ON
USE pubs
IF EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLES
WHERE TABLE_NAME = ‘emp_pay’)
DROP TABLE emp_pay
GO
USE pubs
IF EXISTS (SELECT name FROM sysindexes
WHERE name = ‘employeeID_ind’)
DROP INDEX emp_pay.employeeID_ind
GO
USE pubs
GO
CREATE TABLE emp_pay
(
employeeID int NOT NULL,
base_pay money NOT NULL,
commission decimal(2, 2) NOT NULL
)
INSERT emp_pay
VALUES (1, 500, .10)
INSERT emp_pay
VALUES (2, 1000, .05)
INSERT emp_pay
VALUES (3, 800, .07)
INSERT emp_pay
VALUES (5, 1500, .03)
INSERT emp_pay
VALUES (9, 750, .06)
GO
SET NOCOUNT OFF
CREATE UNIQUE CLUSTERED INDEX employeeID_ind
ON emp_pay (employeeID)
GO

If you have a performance issue on sql transaction, adn you don’t know how to look for it below are the steps that you can use:

1. run sql profiler on the database server that is having performance issue (choose the tuning template provided)

2. look for transaction that takes duration more than the required time.

3. copy the query and paste to sql query analyzer.

4. at the sql query analyzer, press ‘ctrl + L’ (display estimated execution time).

5. look for the total cost of the execution from the diagram normal fast transaction would cost less that 0.XX value.

6. if not, you can create the index. based on the above example. take note you have to change the database name and the column (column take from query example where name = ‘ahb’, column should be ‘name’)

For SQL using IN is very usefull in order to determines if a given value matches any value in a subquery or a list. For example if you want to get certain data from a particular column or field, you can just right below command (in this case my example database is tests , table author and the columns are state and name)

USE tests

SELECT name, state
FROM authors
WHERE state IN (’CH’, ‘MY’, ‘SI’)

This query gives below results:

name state
——– —–
Whiter CH
Greeny CH
Darson CH
Leary CH
Streeght CH
Bannet CH
Deance MY
Strink SI
MacFe CH
Kar SI
Pantel MY
Hunter CA
McBadden CA

(13 row(s) affected)

By using OR to produce the same results of the IN query:

USE tests

SELECT name, state
FROM authors
WHERE state = ‘CH’ OR state = ‘SI’ OR state = ‘MY’

Compare OR and IN , eventhough you get the same results using IN and OR , the next importance things to consider is :

• the time to execute the query considering very huge data (example in the author table, there are 928999 rows)
• the index that you need to create to reduce the execution time

Next tips : Using NOT IN to negates the returned value of IN. also NOT IN versus NOT EXIST