Sponsored Content
Operating Systems Linux Virtualization best practices Post 302813345 by abohmeed on Monday 27th of May 2013 06:09:43 AM
Old 05-27-2013
Virtualization best practices

Hello admins and gurus

I have a controversial topic: now we are investing in a new Linux OS that will hold our Sybase database. The server will virtualized on a VMware server hosted on SAN storage. Now the question is, when we install the database engine is it better - in terms of performance - to put the data files on a separate LUN and connect to it through fiber channel or to create a virtual disk and attach it "locally" to the virtual server as if it was one of it's disks and put the datafiles on it?
In other words, in a virtual word is it better to attach a virtual disk or to connect to a separate LUN provided that both of them are on SAN?
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Scripting Best Practices

Hi - I am new to this and was wondering if some of you can help me out. I am just starting to write scripts and need some guidelines on creating scripts. I'm calling them "Best Practices"...what should I do and not do when creating scripts. All I know so far is that I should avoid putting... (5 Replies)
Discussion started by: toddjameslane
5 Replies

2. Shell Programming and Scripting

Korn Shell Best Practices

I am new to ksh scripts (still reading manuals). I need to write an application that reads a multi-line parameter file, builds sql on-the-fly, runs plsql and saves the output in a specific format for further processing. I am looking for anything on Best Practices for building such an... (1 Reply)
Discussion started by: mtravis
1 Replies

3. UNIX for Advanced & Expert Users

emergency shutdown best practices.

Has anyone implemented or have suggestions on how to shutdown many remote unix/linux servers from a single script initiated from 1 server? I need this to execute in parallel as time is not on my side. Our ups is sadly underrated and will die in approximately 15 minutes. (There is not... (10 Replies)
Discussion started by: jsw371
10 Replies

4. UNIX for Dummies Questions & Answers

Best practices for Source control

Hi all, i am trying to incorporate source control management in my project. We have about 50 - 60 shell scripts on 3 different machines dev, stag and production, but there is no source control. All the files have to be located at specific locations on each machine for it to work I want to... (4 Replies)
Discussion started by: chvs2000
4 Replies

5. Shell Programming and Scripting

Global Script Best Practices

Hey there. I am a relative rookie when it comes to Linux/Unix Administration and have been learning to adapt my meager coding skill to working with shell scripts in the 'nix realms. I have done some exhausting searches for and found plenty of information on making scripts globally available but... (2 Replies)
Discussion started by: Tenuous
2 Replies

6. Solaris

Best practices

Dear all, Kinda lame question but i'd like to hear your experiences and advice. Question in short ----------------- What permission should a mount point "ideally" have - i think it's root. Ex:- /usr/app/ i'd set the app to be owned by root and within /usr/app i would create another... (1 Reply)
Discussion started by: ossupport55
1 Replies
SYBASE_CONNECT(3)														 SYBASE_CONNECT(3)

sybase_connect - Opens a Sybase server connection

SYNOPSIS
resource sybase_connect ([string $servername], [string $username], [string $password], [string $charset], [string $appname], [bool $new = false]) DESCRIPTION
sybase_connect(3) establishes a connection to a Sybase server. In case a second call is made to sybase_connect(3) with the same arguments, no new link will be established, but instead, the link identi- fier of the already opened link will be returned. The link to the server will be closed as soon as the execution of the script ends, unless it's closed earlier by explicitly calling sybase_close(3). PARAMETERS
o $servername - The servername argument has to be a valid servername that is defined in the 'interfaces' file. o $username - Sybase user name o $password - Password associated with $username. o $charset - Specifies the charset for the connection o $appname - Specifies an appname for the Sybase connection. This allow you to make separate connections in the same script to the same data- base. This may come handy when you have started a transaction in your current connection, and you need to be able to do a separate query which cannot be performed inside this transaction. o $new - Whether to open a new connection or use the existing one. RETURN VALUES
Returns a positive Sybase link identifier on success, or FALSE on failure. CHANGELOG
+--------+------------------------------------+ |Version | | | | | | | Description | | | | +--------+------------------------------------+ | 5.3.0 | | | | | | | The $new parameter was added. | | | | | 4.2.0 | | | | | | | The $appname parameter was added. | | | | | 4.0.2 | | | | | | | The $charset parameter was added. | | | | +--------+------------------------------------+ EXAMPLES
Example #1 sybase_connect(3) example <?php $link = sybase_connect('SYBASE', '', '') or die("Could not connect !"); echo "Connected successfully"; sybase_close($link); ?> SEE ALSO
sybase_pconnect(3), sybase_close(3). PHP Documentation Group SYBASE_CONNECT(3)
All times are GMT -4. The time now is 02:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy