Data transfer cost

If I exec a sql command outside azure on another server like
sqlcmd -S sld51cxbyz.database.windows.net -U bleetmaa@sld51cxbyz -P Kj73Bh71D -d MigrationFromAX -Q "exec dbo.runAzureDbJobs"
runAzureDbJobs is a bunch of procs who is merging two tables located inside azure.
What will the data transfer cost? Does the procs executet inside azure or will the data transfer between the external server and azure?
bleetmaa

Hi,
If you Work role and your sql database in the same region, you are not charged.
see this:
Is data transfer between Azure services located within the same region charged?
No. For example, an Azure SQL database in the same region will not have any additional data transfer costs.
If they are in different regions, you could be charged .
Is data transfer between Azure services located in two regions charged?
Yes. Outbound data transfer is charged at the normal rate and inbound data transfer is free.
See the pricing Page:
http://azure.microsoft.com/en-us/pricing/details/data-transfers/
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

Azure Site Recovery to Azure - cost for data transfer and storage

Hello,
I send you this message on behalf of a small firm in Greece interested to implement Azure Site Recovery to Azure.
We have one VM (Windows 2008 R2 Small Business Server) with 2 VHDs (100GB VHD for OS and 550GB VHD for Data) on a Windows 2012 server Std Edition.
I would like to ask you a few questions about the cost of the data transfer and the storage
First: About the initial replication of the VHDs to Azure. It will be 650GBs. Is it free as inbound traffic? If not the Azure Pricing calculator shows about 57€. But there is also the import/export option which costs about the same:
https://azure.microsoft.com/en-us/pricing/details/storage-import-export/
What would be the best solution for our case? Please advice.
Second: What kind of storage is required for the VHDs fo the VM (650GBs). My guess is Blob storage. For this storage locally redundant, the cost will be about 12-13€/month. Please verify.
Third: Is the bandwidth for the replication of our VM to Azure free?
That's all for now.
Thank you in advance.
Kind regards
Harry Arsenidis

Hi Harry,
1st question response: ASR doesn't support Storage Import/Export for seeding the initial replication storage. ASR pricing can be found
here which details about 100GB of Azure replication & storage per VM is included with the purchase of the ASR to Azure subscription SKU through the Microsoft Enterprise Agreement.
Data transfer pricing
here indicates that inbound data transfers are free.
As of now only option will be online replication. What is the current current network link type & bandwidth to Azure? Can you vote for the feature & update requirements here?
2nd question response: A storage account with geo-redundancy is required. But as mentioned earlier with Microsoft Enterprise Agreement you will get 100GB of Azure replication & storage per VM included with ASR.
3rd question response: Covered as part earlier queries.
Regards, Anoob

I am travelling overseas and want to transfer photos from my iPhone to the iPad using iCloud. will this incur data roaming costs?

i am travelling overseas and want to transfer photos from my iPhone to the iPad using iCloud. will this incur data roaming costs?

Yes, unless you are connected to free Wi-Fi.

Legacy data transfer for new depreciation area for already existing assets

Hi all,
I am doing legacy data transfer for New deprecaition area for already existing assets through AS92.
I like to give Ordinay depreciation posted amount for the current FY for these assets in AS92, but i find this field is not editable inAS92.
Please guide me to upload the Posted deprecaiton amount (for current FY) for these assets. I have assets both which are acquired in Last FY year and also this FY year.
Regards,
Srinivas

HI,
I have to migrate Posted dpereciation for new depreciation for nearly 3000 assets, In transaction 147, where i need give Acquituion value aslo, please note these are not new assets, these are prior year assets wiht opeing balances. If we use 147 system will take it is current acquition.
Please note my transter date is 28.02.2010, I have already run AFAB for this company cdoe Feb 2010 for other depreciation areas.
Now i am trying to update Opening APC Cost and Opening Accumulated deprecation for these assets and also posted depreciation for this FY.
Where in AS92, i am able to update Opeing APC Cost and Opeing Acc Dep succsfully for new dep area for already existingassets, bu Posted deprecation field is not editable.
Please guide me how to update posted deprecation for new deprecaition area in AS92 or some other way for already existing assets.
REgards,
Srinivas

Internal Disk to Disk Data Transfer Speed Very Slow

I have a G5 Xserve running Tiger with all updates applied that has recently started experiencing very slow Drive to Drive Data transfer speeds.
When transferring data from one drive to another ( Internal to Internal, Internal to USB, Internal, Internal to FW, USB to USB or any other combination of the three ) we only are getting about 2GB / hr transfer speeds.
I initially thought the internal drive was going bad. I tested the drive and found some minor header issues etc... that were able to be repaired so I replace the internal boot drive
I tested and immediately got the same issue.
I also tried booting from a FW drive and I got the same issue.
If I connect to the server over the ethernet network, I get what I would expect to be typical data transfer rates of about 20GB+ / hr. Much higher than the internal rates and I am copying data from the same internal drives so I really don't think the drive is the issue.
I called AppleCare and discussed the issue with them. They said it sounded like a controller issue so I purchased a replacement MLB from them. After replacing the drive data transfer speeds jumped back to normal for about a day maybe two.
Now we are back to experiencing slow data transfer speeds internally ( 2GB / hr ) and normal transfer speeds ( 20GB+ / hr ) over the network.
Any ideas on what might be causing the problem would be appreciated

As suggested, do check for other I/O load on the spindles. And check for general system load.
I don't know of a good GUI in-built I/O monitor here (and particularly for Tiger Server), though there is iopending and DTrace and Apple-provided [performance scripts|http://support.apple.com/kb/HT1992] with Leopard and Leopard Server. top would show you busy processes.
Also look for memory errors and memory constraints and check for anything interesting in the contents of the system logs.
The next spot after the controllers (and it's usually my first "hardware" stop for these sorts of cases, and usually before swapping the motherboard) are the disks that are involved, and whatever widgets are in the PCI slots. Loose cables, bad cables, and spindle-swaps. Yes, disks can sometimes slow down like this, and that's not usually a Good Thing. I know you think this isn't the disks, but that's one of the remaining common hardware factors. And don't presume any SMART disk monitoring has predictive value; SMART can miss a number of these cases.
(Sometimes you have to use the classic "field service" technique of swapping parts and of shutting down software pieces until the problem goes away. Then work from there.)
And the other question is around how much time and effort should be spent on this Xserve G5 box; whether you're now in the market for a replacement G5 box or a newer Intel Xserve box as a more cost-effective solution.
(How current and how reliable is your disk archive?)

Data Transfer methods

Hi all,
Can anyone please explain me what are synchronous and asychronous data transfer methods?
Where are the settings to be done in R/3 to get data to BI ?
Thanks in advance

Data Transfer
Definition
Synchronous Data Transfer
Data is transferred directly (simultaneously, synchronously) from program to program via CPI-C communication.
Both communications partners must be available at the same time. Because the central SAP system in a typical SAP installation does not run round the clock, but the linked systems are frequently in operation 24 hours a day, asynchronous data transfer is necessary.
Synchronous data transfer has the following disadvantages:
Transfer is not possible is the partner system or the line is not available.
A data backlog in the reciever system causes a data backlog in the sender system. Processing in the application is delayed.
If a connection is broken, it may be necessary to perform a recovery in both systems.
Asynchronous Data Transfer
With asynchronous, or buffered, data transfer, data is temporarily stored in a sequential queue.
Asynchronous transfer has the following advantages:
Wait times in the sender system are avoided.
A recovery is automatically performed in the sender system.
Transfer need not be performed during online time. This avoids placing unnecessary load on the system and thus helps to reduce costs.
The Queue Application Programming Interface (Q-API) is an SAP interface for asynchronous data transfer.
Data is buffered sequentially and processed immediately or later by an asynchronously running process.
One possible processing method is to send data to an external partner system via CPI-C. Data units that belong together can be stored in accordance with transaction and sent to a communications partner.
Data is buffered in queues before it is transferred to the target system.
In an R/3 System, the queues are stored in a relational database. All R/3 database systems are supported.

CJR2-The plan data transfer is locked

Hi,
I am planning costs by CJR2 on a WBS element for a certain period and version by cost element.When I execute CJR2,it allows me to enter the values against periods but when I try to save ,system gives error message-The plan data transfer is locked for fiscal year 2009 and version F06 in controlling area 1000.
I have checked in OKP1 and also in CO versions,this version is not locked for any transactions and Fiscal year 2009.Has anyone come accross similar situation and how was it resolved.
Its matter of urgency,any help will be highly appreciated.
Regards,
MTH

Hi Ravi,
Thanks for your answer.I have checked the statuses and there are no status hampering the Plan primary cost or Periodic reposting Plan data.I guess its more related to the version used.Any other thoughts?Anyone.....
Regards,
MTH

Data Transfer HR

Hi Gurus,
i have a problem about data transfer HR. I have registred hours in HR Time Sheet and approval this hours. There is a way to transfer this data on PP order???
Thanks
Nicola

Hi Nicola,
Unfortunately, as far as I know, time recording in HR is not integrated with PP. First and foremost, there no indication of the PP order when you report attendance in HR, so there's no basis of relating the two.
I think that you need to report execution hours to PP orders only if you need an actual cost collection per order. And if you do this, and HR attendance, you can reconcile the hours on the cost center level, to see that PP report makes sense versus time attendance.
Regards,
Mario

Hi Data transfer methods for ABAP Dataflow

HI
Good Day !!!!
Can any one Explain about What are Data tansfer mothods in ABAP Dataflow Explain Each one which is the best one can you explain with example .
Regards
Chandu

Data Transfer
Definition
Synchronous Data Transfer
Data is transferred directly (simultaneously, synchronously) from program to program via CPI-C communication.
Both communications partners must be available at the same time. Because the central SAP system in a typical SAP installation does not run round the clock, but the linked systems are frequently in operation 24 hours a day, asynchronous data transfer is necessary.
Synchronous data transfer has the following disadvantages:
Transfer is not possible is the partner system or the line is not available.
A data backlog in the reciever system causes a data backlog in the sender system. Processing in the application is delayed.
If a connection is broken, it may be necessary to perform a recovery in both systems.
Asynchronous Data Transfer
With asynchronous, or buffered, data transfer, data is temporarily stored in a sequential queue.
Asynchronous transfer has the following advantages:
Wait times in the sender system are avoided.
A recovery is automatically performed in the sender system.
Transfer need not be performed during online time. This avoids placing unnecessary load on the system and thus helps to reduce costs.
The Queue Application Programming Interface (Q-API) is an SAP interface for asynchronous data transfer.
Data is buffered sequentially and processed immediately or later by an asynchronously running process.
One possible processing method is to send data to an external partner system via CPI-C. Data units that belong together can be stored in accordance with transaction and sent to a communications partner.
Data is buffered in queues before it is transferred to the target system.
In an R/3 System, the queues are stored in a relational database. All R/3 database systems are supported.

NI8451 SPI data transfer speed and SCLK setup time adjustment

I'm using NI USB-8451 SPI bus to do communication. I can not reach the speed of communication 4MHz (NI USB-8451 module advertises speeds up to 12MHz). Actrually the data transfer speed is much slower than 4/8 Mb/s. The 16k*16bit data cost around 800ms while it should be 128ms if the data transfer achieves 4Mhz speed. In the manual there is a SPI timing clock figure like this:
In the 4Mhz communication case, the t2 should be 0.25us. I wonder whether the low data transfer speed is due to t1,t3 and t4 since they occupy too much "dead time". If my guess is right, is there any method to reduce the t1,t3 or t4, espetially t3? I know that in the advanced API there is a way to add delay while I did not figure out how to reduce delay(t3). If my guess is wrong, what is the exactly maximum data transfer speed NI8451 can support? (not the clock rate)
Thanks for help.

Hi everyone. Im using the SPI communication with 8451 and Im having the same situation., since the serial flash memory I need to program is big enough, t3 (SCLK Setup time) and other "dead time" which I think is the time when buffer on the 8451 needs to be re-filled those are killing my expectation on the final results. I can't see a way to decrease t3 (~10uSec) and in the same way Im seeing something like buffering up to 100~110 bytes then, a ~1.5mSec delay appears on the signal waveforms. Did somebody have good results trying to avoid this?
Thank you.
Javier
Attachments:
t3 - SCLK setup time.jpg ‏156 KB
Data byte Transfer_109.jpg ‏137 KB

Net Book Value calculation Issue Manual Legacy Data Transfer

Dear All
I want to Upload balance of old fixed Asset in newly configure System that are managed manually in previous year, I want to Post Their previous Current Written Down Value and Current Accumulated Depreciation when i go via IMG Create Legacy Data Transfer and enter,
Take Over Value of assets I entered for example
Accusation Value 100,000
Accumulated ordinary depreciation (Old depreciation in Previous Years) RS.10,000
Net book Value Rs.110,000
and system Calculate the Depreciation on 110,000 as WDV 10% that is 11,000
My requirement is that it will Calculate it as 100000-10000
Depreciation should be calculated at a 90000 @ 10% WDV that is 9000
Please suggest me, how i can do.
or other path or T.code where i can do.
i am new please explain in detail.
Regard
Khalid mahmood

Dear Atif and AP
Issue is not with Depreciation key it is working well according to my requirement but the issue is that base value that the system use is wrong.
i want that the system calculate depreciation at Cumulative Acquisition value (Purchase /capitalize/ cost price) less Accumulated Depreciation
is equals to Written Down Value.
I want that system use WDV as a base in each year after deducting year depreciation or (Acqusition cost - Accumulated depreciation).
I post a new asset and assign depreciation key it working well as required.
But i going to post Old asset for example Rs.100000 in year 2006. its Accumulated depreciation is suppose Rs.30000 in Year end 2011.
i want to post that asset in year 2012 as 100000-30000 and WDV IS Rs.70000 ;
i want that it will use 70000 as a base in the coming year to calculate depreciation.
My response is 100000+30000 and use 130000 as base to calculate the ordinary depreciation for the next year.
Now Please read the first thread again and guide me according to my scenario.
or tell me how i post the old asset value and their depreciation.
Regard
Khalid Mahmood

Firewire and Data Transfer

I'll be purchasing the new Mini and had 2 questions. 1- is the file/data transfer migration program a good one? I have lots of info I need transfered and I am concerned everything will be moved correctly. 2- The firewire port on the new Mini is 800. After I purchase an adaptor - 800 to 400 - I have a bunch of external HDs (all self-powered) - is it okay to simply daisy-chain them or should I purchase a firewire hub?
Thank you.
Rich Green

hub or daisy-chain
I would always tend to recommend a hub in this situation if it is viable, since this eliminates potential FW conflicts, and can resolve odd issues which daisy chains can cause. However, there is nothing wrong with experimenting - if you have the FW devices, I'd try the daisy chain first since it doesn't cost anything. If there are any signs of issues (devices not accessible or 'dropping out' of the chain, then you know to get a hub and try again.

Data transfer legacy

dear all
Can eny one tell me about data transfer legacy?
How are modules interagted and what are means of data transfer for intra module.
Thanks in advance.

Hi,
You would use LSMW to upload master data and either BDC/BAPI for uploading transaction data.
Visit the following link:
Re: sap general
Where you would find more information about BDC and LSMW.
For information regarding LSMW steps visit the following link:
/people/hema.rao/blog/2006/09/14/lsmw--step-by-step
http://help.sap.com/bp_blv1500/BL_US/html/dataconv_lsmw.htm
The SAP System consists of a number of components that are completely integrated with one another. This integration allows the various departments and units of an enterprise to share and maintain the same information.
Purchasing is a component of Materials Management (MM). The Materials Management (MM) module is fully integrated with the other modules of the SAP System. It supports all the phases of materials management: materials planning and control, purchasing, goods receiving, inventory management, and invoice verification.
The tasks of the MM Purchasing component are as follows:
    External procurement of materials and services
    Determination of possible sources of supply for a requirement identified by the materials planning and control system or arising directly within a user department
    Monitoring of deliveries from and payments to vendors
Good communication between all participants in the procurement process is necessary for Purchasing to function smoothly.
<b>Integration</b>
Purchasing communicates with other modules in the SAP System to ensure a constant flow of information. For example, it works side by side with the following modules:
    Controlling (CO)
The interface to the cost accounting system (Controlling) can be seen above all in the case of purchase orders for materials intended for direct consumption and for services, since these can be directly assigned to a cost center or a production order.
    Financial Accounting (FI)
Purchasing maintains data on the vendors that are defined in the system jointly with Financial Accounting. Information on each vendor is stored in a vendor master record, which contains both accounting and procurement information. The vendor master record represents the creditor account in financial accounting.
Through PO account assignment, Purchasing can also specify which G/L accounts are to be charged in the financial accounting system.
    Sales and Distribution (SD)
Within the framework of materials planning and control, a requirement that has arisen in the Sales area can be passed on to Purchasing. In addition, when a requisition is created, it can be directly assigned to a sales order.
http://help.sap.com/saphelp_erp2005/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Hope this will help.
Regards,
Naveen.

I'm running out of data transfer space?

Anyone help me understand how this fills up, and what it's caused by? I have a QT short movie on my iWebsite, if it matters. Says,
"You are currently using 3.82 GB of 5 GB bimonthly data transfer limit. Find out more about data transfer limits."

Upgrading to the family pack still only gives you 1GB of space, no idea what the data transfer is, but probably still 10GB/month.
From .mac help:
Adding storage
If you're a .Mac member, You can increase your combined email and iDisk storage to a total of 2 GB or 4 GB by purchasing more storage.
Note: If you have a trial membership, email-only account, or Family Pack sub-account, you cannot increase your storage amount.
The cost of upgrading your combined email and iDisk storage is determined by the time remaining in your yearly membership and the amount of storage you already have. For example, if you upgrade your storage space six months before your renewal date, you pay only half the yearly fee.
The cost of the additional space is charged to your credit card. Your purchase will renew automatically as part of your account subscription each year. For pricing information, see ".Mac pricing" in the Membership section of .Mac Help.
To add storage:
1. Go to www.mac.com and log in.
2. Click your member name on the .Mac tab, and then confirm your login.
3. Click Buy More on your Account Settings page.
4. Choose an upgrade option from the Storage pop-up menu, and then click Continue.
5. Review your billing information and click Continue.
6. Review your order and click Buy Now.
7.
8. Wait while your order is processed (it only takes a moment). Don't use your browser to view another page until you see your purchase confirmation.
After you see your purchase confirmation, it takes a few minutes before your new storage is available. When you upgrade your storage, the additional storage you purchased is allocated to your personal iDisk. To learn about setting different storage capacities for .Mac Mail and your iDisk, see "Designating storage."
Your best bet is to add storage, as this increases your bandwith as well,
Upgrade to 2GB of storage = 25GB/month
Upgrade to 4GB of storage = 250GB/month
Follow the steps above (1-4) and it will show you the price for your part of the world.
Will
1GHz G4, 15" PB, 1.5GB RAM, Airport Network, 4 GB iPod Mini (1G), 60GB iPod (5G) Mac OS X (10.4.6)
Help others by marking solved questions as answered ( + Solved or Helpful )

How to find the max data transfer rate(disk speed) supported by mobo?

I plan on replacing my current HDD with a new and bigger HDD.
For this I need to know the max data transfer rate(disk speed) that my mobo will support. However, dmidecode is not telling me that. Am I missing something?
Here's dmidecode:
# dmidecode 2.11
SMBIOS 2.5 present.
80 structures occupying 2858 bytes.
Table at 0x000F0450.
Handle 0xDA00, DMI type 218, 101 bytes
OEM-specific Type
Header and Data:
DA 65 00 DA B2 00 17 4B 0E 38 00 00 80 00 80 01
00 02 80 02 80 01 00 00 A0 00 A0 01 00 58 00 58
00 01 00 59 00 59 00 01 00 75 01 75 01 01 00 76
01 76 01 01 00 05 80 05 80 01 00 D1 01 19 00 01
00 15 02 19 00 02 00 1B 00 19 00 03 00 19 00 19
00 00 00 4A 02 4A 02 01 00 0C 80 0C 80 01 00 FF
FF 00 00 00 00
Handle 0xDA01, DMI type 218, 35 bytes
OEM-specific Type
Header and Data:
DA 23 01 DA B2 00 17 4B 0E 38 00 10 F5 10 F5 00
00 11 F5 11 F5 00 00 12 F5 12 F5 00 00 FF FF 00
00 00 00
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A17
Release Date: 04/06/2010
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 4096 kB
Characteristics:
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
EDD is supported
Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
BIOS Revision: 17.0
Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: OptiPlex 755
Version: Not Specified
UUID: 44454C4C-5900-1050-8033-C4C04F434731
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified
Handle 0x0200, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Dell Inc.
Product Name: 0PU052
Version:
Handle 0x0300, DMI type 3, 13 bytes
Chassis Information
Manufacturer: Dell Inc.
Type: Space-saving
Lock: Not Present
Version: Not Specified
Asset Tag:
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
Handle 0x0400, DMI type 4, 40 bytes
Processor Information
Socket Designation: CPU
Type: Central Processor
Family: Xeon
Manufacturer: Intel
ID: 76 06 01 00 FF FB EB BF
Signature: Type 0, Family 6, Model 23, Stepping 6
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Not Specified
Voltage: 0.0 V
External Clock: 1333 MHz
Max Speed: 5200 MHz
Current Speed: 2666 MHz
Status: Populated, Enabled
Upgrade: Socket LGA775
L1 Cache Handle: 0x0700
L2 Cache Handle: 0x0701
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 2
Core Enabled: 2
Thread Count: 2
Characteristics:
64-bit capable
Handle 0x0700, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 32 kB
Maximum Size: 32 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: None
System Type: Data
Associativity: 8-way Set-associative
Handle 0x0701, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 6144 kB
Maximum Size: 6144 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: <OUT OF SPEC>
Handle 0x0800, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: PARALLEL
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-25 female
Port Type: Parallel Port PS/2
Handle 0x0801, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SERIAL1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x0802, DMI type 126, 9 bytes
Inactive
Handle 0x0803, DMI type 126, 9 bytes
Inactive
Handle 0x0804, DMI type 126, 9 bytes
Inactive
Handle 0x0805, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0806, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB2
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0807, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB3
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0808, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB4
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0809, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB5
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB6
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB7
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB8
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: ENET
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: RJ-45
Port Type: Network Port
Handle 0x080E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MIC
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x080F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0810, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-IN
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0811, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: HP-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0812, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MONITOR
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x090A, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT1
Type: x1 Proprietary
Current Usage: In Use
Length: Long
Characteristics:
PME signal is supported
Handle 0x0901, DMI type 126, 13 bytes
Inactive
Handle 0x0902, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT2
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 2
Characteristics:
5.0 V is provided
3.3 V is provided
PME signal is supported
Handle 0x0903, DMI type 126, 13 bytes
Inactive
Handle 0x0904, DMI type 126, 13 bytes
Inactive
Handle 0x0905, DMI type 126, 13 bytes
Inactive
Handle 0x0906, DMI type 126, 13 bytes
Inactive
Handle 0x0907, DMI type 126, 13 bytes
Inactive
Handle 0x0908, DMI type 126, 13 bytes
Inactive
Handle 0x0A00, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Disabled
Description: Intel Graphics Media Accelerator 950
Handle 0x0A02, DMI type 10, 6 bytes
On Board Device Information
Type: Ethernet
Status: Enabled
Description: Intel Gigabit Ethernet Controller
Handle 0x0A03, DMI type 10, 6 bytes
On Board Device Information
Type: Sound
Status: Enabled
Description: Intel(R) High Definition Audio Controller
Handle 0x0B00, DMI type 11, 5 bytes
OEM Strings
String 1: www.dell.com
Handle 0x0D00, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x0F00, DMI type 15, 29 bytes
System Event Log
Area Length: 2049 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: Memory-mapped physical 32-bit address
Access Address: 0xFFF01000
Status: Valid, Not Full
Change Token: 0x00000018
Header Format: Type 1
Supported Log Type Descriptors: 3
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: System limit exceeded
Data Format 2: System management
Descriptor 3: Log area reset/cleared
Data Format 3: None
Handle 0x1000, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 4
Handle 0x1100, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_1
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Manufacturer: AD00000000000000
Handle 0x1101, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_3
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1102, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_2
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1103, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_4
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1300, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FDFFFFFF
Range Size: 4064 MB
Physical Array Handle: 0x1000
Partition Width: 1
Handle 0x1400, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1100
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1401, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1101
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1402, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1102
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1403, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1103
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1410, DMI type 126, 19 bytes
Inactive
Handle 0x1800, DMI type 24, 5 bytes
Hardware Security
Power-On Password Status: Enabled
Keyboard Password Status: Not Implemented
Administrator Password Status: Enabled
Front Panel Reset Status: Not Implemented
Handle 0x1900, DMI type 25, 9 bytes
System Power Controls
Next Scheduled Power-on: *-* 00:00:00
Handle 0x1B10, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD00
Handle 0x1B11, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD01
Handle 0x1B12, DMI type 126, 12 bytes
Inactive
Handle 0x1B13, DMI type 126, 12 bytes
Inactive
Handle 0x1B14, DMI type 126, 12 bytes
Inactive
Handle 0x2000, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected
Handle 0x8100, DMI type 129, 8 bytes
OEM-specific Type
Header and Data:
81 08 00 81 01 01 02 01
Strings:
Intel_ASF
Intel_ASF_001
Handle 0x8200, DMI type 130, 20 bytes
OEM-specific Type
Header and Data:
82 14 00 82 24 41 4D 54 01 01 00 00 01 A5 0B 02
00 00 00 00
Handle 0x8300, DMI type 131, 64 bytes
OEM-specific Type
Header and Data:
83 40 00 83 14 00 00 00 00 00 C0 29 05 00 00 00
F8 00 4E 24 00 00 00 00 0D 00 00 00 02 00 03 00
19 04 14 00 01 00 01 02 C8 00 BD 10 00 00 00 00
00 00 00 00 FF 00 00 00 00 00 00 00 00 00 00 00
Handle 0x8800, DMI type 136, 6 bytes
OEM-specific Type
Header and Data:
88 06 00 88 5A 5A
Handle 0xD000, DMI type 208, 10 bytes
OEM-specific Type
Header and Data:
D0 0A 00 D0 01 03 FE 00 11 02
Handle 0xD100, DMI type 209, 12 bytes
OEM-specific Type
Header and Data:
D1 0C 00 D1 78 03 07 03 04 0F 80 05
Handle 0xD200, DMI type 210, 12 bytes
OEM-specific Type
Header and Data:
D2 0C 00 D2 F8 03 04 03 06 80 04 05
Handle 0xD201, DMI type 126, 12 bytes
Inactive
Handle 0xD400, DMI type 212, 242 bytes
OEM-specific Type
Header and Data:
D4 F2 00 D4 70 00 71 00 00 10 2D 2E 42 00 11 FE
01 43 00 11 FE 00 0F 00 25 FC 00 10 00 25 FC 01
11 00 25 FC 02 12 00 25 FC 03 00 00 25 F3 00 00
00 25 F3 04 00 00 25 F3 08 00 00 25 F3 0C 07 00
23 8F 00 08 00 23 F3 00 09 00 23 F3 04 0A 00 23
F3 08 0B 00 23 8F 10 0C 00 23 8F 20 0E 00 23 8F
30 0D 00 23 8C 40 A6 00 23 8C 41 A7 00 23 8C 42
05 01 22 FD 02 06 01 22 FD 00 8C 00 22 FE 00 8D
00 22 FE 01 9B 00 25 3F 40 9C 00 25 3F 00 09 01
25 3F 80 A1 00 26 F3 00 A2 00 26 F3 08 A3 00 26
F3 04 9F 00 26 FD 02 A0 00 26 FD 00 9D 00 11 FB
04 9E 00 11 FB 00 54 01 23 7F 00 55 01 23 7F 80
5C 00 78 BF 40 5D 00 78 BF 00 04 80 78 F5 0A 01
A0 78 F5 00 93 00 7B 7F 80 94 00 7B 7F 00 8A 00
37 DF 20 8B 00 37 DF 00 03 C0 67 00 05 FF FF 00
00 00
Handle 0xD401, DMI type 212, 172 bytes
OEM-specific Type
Header and Data:
D4 AC 01 D4 70 00 71 00 03 40 59 6D 2D 00 59 FC
02 2E 00 59 FC 00 6E 00 59 FC 01 E0 01 59 FC 03
28 00 59 3F 00 29 00 59 3F 40 2A 00 59 3F 80 2B
00 5A 00 00 2C 00 5B 00 00 55 00 59 F3 00 6D 00
59 F3 04 8E 00 59 F3 08 8F 00 59 F3 00 00 00 55
FB 04 00 00 55 FB 00 23 00 55 7F 00 22 00 55 7F
80 F5 00 58 BF 40 F6 00 58 BF 00 EB 00 55 FE 00
EA 00 55 FE 01 40 01 54 EF 00 41 01 54 EF 10 ED
00 54 F7 00 F0 00 54 F7 08 4A 01 53 DF 00 4B 01
53 DF 20 4C 01 53 7F 00 4D 01 53 7F 80 68 01 56
BF 00 69 01 56 BF 40 FF FF 00 00 00
Handle 0xD402, DMI type 212, 152 bytes
OEM-specific Type
Header and Data:
D4 98 02 D4 70 00 71 00 00 10 2D 2E 2D 01 21 FE
01 2E 01 21 FE 00 97 00 22 FB 00 98 00 22 FB 04
90 00 11 CF 00 91 00 11 CF 20 92 00 11 CF 10 E2
00 27 7F 00 E3 00 27 7F 80 E4 00 27 BF 00 E5 00
27 BF 40 D1 00 22 7F 80 D2 00 22 7F 00 45 01 22
BF 40 44 01 22 BF 00 36 01 21 F1 06 37 01 21 F1
02 38 01 21 F1 00 39 01 21 F1 04 2B 01 11 7F 80
2C 01 11 7F 00 4E 01 65 CF 00 4F 01 65 CF 10 D4
01 65 F3 00 D5 01 65 F3 04 D2 01 65 FC 00 D3 01
65 FC 01 FF FF 00 00 00
Handle 0xD403, DMI type 212, 157 bytes
OEM-specific Type
Header and Data:
D4 9D 03 D4 70 00 71 00 03 40 59 6D 17 01 52 FE
00 18 01 52 FE 01 19 01 52 FB 00 1A 01 52 FB 04
1B 01 52 FD 00 1C 01 52 FD 02 1D 01 52 F7 00 1E
01 52 F7 08 1F 01 52 EF 00 20 01 52 EF 10 21 01
52 BF 00 22 01 52 BF 40 87 00 59 DF 20 88 00 59
DF 00 E8 01 66 FD 00 E9 01 66 FD 02 02 02 53 BF
00 03 02 53 BF 40 04 02 53 EF 00 05 02 53 EF 10
06 02 66 DF 00 07 02 66 DF 20 08 02 66 EF 00 09
02 66 EF 10 17 02 66 F7 00 18 02 66 F7 08 44 02
52 BF 40 45 02 52 BF 00 FF FF 00 00 00
Handle 0xD800, DMI type 126, 9 bytes
Inactive
Handle 0xDD00, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 00 DD 00 01 00 00 00 10 F5 00 00 00 00 00
00 00 00
Handle 0xDD01, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 01 DD 00 01 00 00 00 11 F5 00 00 00 00 00
00 00 00
Handle 0xDD02, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 02 DD 00 01 00 00 00 12 F5 00 00 00 00 00
00 00 00
Handle 0xDE00, DMI type 222, 16 bytes
OEM-specific Type
Header and Data:
DE 10 00 DE C1 0B 00 00 10 05 19 21 01 00 00 01
Handle 0x7F00, DMI type 127, 4 bytes
End Of Table
Hdparm also does not tell me the max data transfer rate (disk speed) of my current drive although this link : www.wdc.com/en/library/sata/2879-001146.pdf says that it is 3.0Gb/s
and here's hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: WDC WD800JD-75JNC0
Firmware Revision: 06.01C06
Standards:
Supported: 6 5 4
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156250000
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 76293 MBytes
device size with M = 1000*1000: 80000 MBytes (80 GB)
cache/buffer size = 8192 KBytes
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 8
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
SET_MAX security extension
Automatic Acoustic Management feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* SMART error logging
* SMART self-test
* Gen1 signaling speed (1.5Gb/s)
* Host-initiated interface power management
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
Checksum: correct
Last edited by Inxsible (2011-03-27 04:40:49)

I just checked my BIOS and my current setting is set at IDE although it also mentions that the default should be AHCI. Currently I have a dual boot of Windows 7 (need it for Tax software) and Arch
So I guess, when I get the new HDD, I will first set it to AHCI and then install the OSes on it. See if NCQ helps any, and if not I will turn it back and re-install (if I have to). I am planning to have Windows only in virtualbox in the new drive.
Anyhoo, while I was in the BIOS I found two things which I had questions about :
1) Under Onboard Devices --> Integrated NIC , my setting is currently set at "On w/PXE" and it says the default should be just "On". Would it be ok to change it back to On since its a single machine and its not booting an OS on any server. I just don't want to have to re-install anything now since I will be doing that in the new HDD.
2) How would I know whether my BIOS would support a 64 bit OS in Virtualbox? I checked some setting under Virtualization, but they weren't very clear.
I will edit this post and let you know exactly what settings were present under the Virtualization sub-section.

Data transfer cost

Similar Messages

Maybe you are looking for