Basically, you have to install the Oracle client software on your SQL server, then using references in the tnsnames.ora file, you create the linked server using the "Oracle Provider for Ole DB" driver.
Reference:
http://gleew.wordpress.com/2008/03/19/sql-server-linked-server-to-oracle/
Wednesday, April 25, 2012
How to create linked server to Oracle
Monday, March 19, 2012
Migrating SQL Reporting Services
Good article.
Reference:
http://www.mssqltips.com/sqlservertip/2627/migrating-sql-reporting-services-to-a-new-server/
http://www.sqldbatips.com/showarticle.asp?ID=62
Reference:
http://www.mssqltips.com/sqlservertip/2627/migrating-sql-reporting-services-to-a-new-server/
http://www.sqldbatips.com/showarticle.asp?ID=62
Tuesday, March 6, 2012
Dynamically create redirected folders
Thursday, February 23, 2012
Editting HOSTS file in Win 7
Basically, you "run as Administrator" NOTEPAD, open HOSTS, edit and save.
Reference:
http://support.microsoft.com/kb/923947
Reference:
http://support.microsoft.com/kb/923947
Wednesday, February 22, 2012
How to offline a volume in Windows Server
I wanted to offline a volume so I could remove HD from virtual servers. Found this command:
mountvol E: /p
Worked well.
Reference:
http://technet.microsoft.com/en-us/library/cc772671.aspx
mountvol E: /p
Worked well.
Reference:
http://technet.microsoft.com/en-us/library/cc772671.aspx
Monday, February 6, 2012
VM will not power on
One of my VMs would not power up. The error it was giving was:
"Cannot open the disk '/vmfs/volumes/......vmdk' or one of the snapshot disks it depends on. Reason: Argument list too long."
I went into "Edit Settings" for the VM and found that hard disk 2 was referencing was not valid, an empty file. I removed the hard disk, and re-added the hard disk, but pointing to the correct VMDK file.
After that the VM started up just fine.
Reference:
http://vkarthickeyan.wordpress.com/2011/12/29/virtual-machine-not-powered-on/
"Cannot open the disk '/vmfs/volumes/......vmdk' or one of the snapshot disks it depends on. Reason: Argument list too long."
I went into "Edit Settings" for the VM and found that hard disk 2 was referencing was not valid, an empty file. I removed the hard disk, and re-added the hard disk, but pointing to the correct VMDK file.
After that the VM started up just fine.
Reference:
http://vkarthickeyan.wordpress.com/2011/12/29/virtual-machine-not-powered-on/
Friday, January 20, 2012
VMware: IP address already assigned to another adapter
To resolve this issue, make the ghosted network adapter visible in the Device Manager and uninstall the ghosted network adapter from the registry:
- Select Start > Run, type cmd.exe, and press Enter.
- At the command prompt, run this command: "set devmgr_show_nonpresent_devices=1"
- Enter Start DEVMGMT.MSC and press Enter to start Device Manager.
- Select View > Show Hidden Devices.
- Expand the Network Adapters tree (select the plus sign next to the Network adapters entry).
- Right-click the dimmed network adapter, and then click Uninstall.
- Close Device Manager.
Reference:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1179
Subscribe to:
Posts (Atom)