Anda di halaman 1dari 5

Morfologi dan Daur Hidup

Cacing Dewasa
Cacing betina berukuran 8-13 mm x 0,3-0,5 mm, dengan pelebaran kutikulum seperti sayap pada ujung
anterior yang disebut alae. Bulbus oesofagus jelas sekali, dan ekor runcing. Pada cacing betina gravid,
uterus melebar dan penuh telur.

Gambar 1: E.vermicularis betina
Cacing jantan lebih kecil sekitar 2-5 mm dan juga bersayap, tapi ekornya berbentuk seperti tanda tanya,
spikulum pada ekor jarang ditemukan.
Gambar 2: E.vermicularis jantan
Telur E. vermicularis
Telur E. vermicularis oval, tetapi asimetris (membulat pada satu sisi dan mendatar pada sisi yang lain),
dinding telur terdiri atas hialin, tidak berwarna dan transparan, serta rerata panjangnya x diameternya
47,83 x 29,64 mm (Brown, 1979). Telur cacing ini berukuran 50m - 60m x 30m, berbentuk lonjong
dan lebih datar pada satu sisinya (asimetris). Dinding telur bening dan agak tebal, didalamnya berisi
massa bergranula berbentuk oval yang teratur, kecil, atau berisi embrio cacing, suatu larva kecil yang
melingkar.

Gambar 3: Telur E. vermicularis
Habitat cacing dewasa biasanya biasanya di rongga sekum, usus besar dan di usus halus yang
berdekatan dengan rongga sekum. Makanannya adalah isi usus.

Gambar 4: potongan melintang E. vermicularis dewasa di usus halus
Cacing betina yang gravid mengandung 11.000-15.000 butir telur, bermigrasi ke daerah perianal untuk
bertelur dengan cara kontraksi uterus dan vaginanya. Telur-telur jarang dikeluarkan di usus sehingga
jarang ditemukan di tinja. Telur menjadi matang dalam waktu 6 jam setelah dikeluarkan. Telur resisten
terhadap desinfektan dan udara dingin. Dalam keadaan lembab telur dapat hidup sampai 13 hari.
Kopulasi cacing jantan mati setelah kopulasi dan cacing betina mati setelah bertelur.
You can click the Edit Mappings button (on the Select Source Tables and Views dialog) to
review the column mappings from the data source to the data destination as shown below. If
the table does not exist in the destination data source, you can also edit the mappings.

You can click the option to drop and recreate the table in the destination data source; by default
this option is unchecked. You can click Enable identity insert if the destination table has an
identity column and the data source has values that you want to assign to the identity column. If
the table does not exist in the destination data source, the Create destination table radio button
will be selected and the other radio buttons will be disabled. If the table already exists in the
destination data source, the Create destination table radio button will be disabled and you can
select either the Delete or Append options.
You can click the Edit SQL button to review and/or edit the SQL to create the table in the
destination data source as shown below:

Click OK twice to return to the Select Source Tables and Views dialog, then click Next to
proceed to the Save and Execute Package dialog.
Save and Execute Package
The Save and Execute Package dialog gives you options to perform the import operation and to
create an SSIS package and save it to SQL Server or the file system as shown below:

For our purposes we will save the SSIS package. Click Next to proceed to the Save SSIS
Package dialog.
Save SSIS Package
The Save SSIS Package is invoked if you chose to save your import operation as an SSIS
package on the Save and Execute Package dialog. Fill in the dialog as shown below:

Click Next to proceed to the Complete the Wizard dialog.
Complete the Wizard
The Complete the Wizard dialog shows a summary of the options that you have chosen for the
import operation as shown below:
Create a Server Role in T-SQL
To create a server role called "juniordba" use the following:
USE master
GO
CREATE SERVER ROLE juniordba

Next we will create a login called Brady and then add it to the new juniordba role that was
created:
USE master
GO
ALTER SERVER ROLE juniordba ADD MEMBER Brady

We haven't added any permissions to the server role, so Brady shouldn't have access. To test
this we can login as Brady and run the following query:
SELECT * FROM sys.dm_exec_connections

As you can see we get the following error message:
Msg 297, Level 16, State 1, Line 1 The user does not have permission to perform this
action.
Next, I'll assign permissions to the server role that will allow Brady to run DMV's.
GRANT CONNECT SQL TO juniordba
GRANT VIEW ANY DATABASE TO juniordba
GRANT VIEW ANY DEFINITION TO juniordba
GRANT VIEW SERVER STATE to juniordba