SQL Server 2005 Std. Best practice for VCenter 4 deployment

[AlbertWT]

Hi All,

May I know what sort of database criteria / best practice that i need to create in order to support VCenter Management Server v4 ?

I'm using Windows Server 2003 Std. and SQL Server 2005 SP3 Standard edition.

Thanks.

Kind Regards,

AWT

[krowczynski]

Hi,

first take a look at the matrix which are compatible.

If you have an existing SQL Server use him, for small enviroment you can use the SQL Express.

MCP, VCP

[AlbertWT]

Hi Krow,

Thanks for replying to this thread,I'm now at the stage of creating a separate DB from SSMS since i'm hesitant to point to the existing (Servername\WSUSDB) because this Database will also be queried by others such as *Veeam Reporting

tools*, therefore i need to set the details logging into level 3 (out of

6). I tried with SQL Express 2005 and it is very slow.

Kind Regards,

AWT

[krowczynski]

If SQLExpress is too slow for you, you should make a seperate instance for vcenter and leave a seperate for WSUSDB.

MCP, VCP

[AlbertWT]

OK, how about the detailed settings ?

such as Permission, Shrink option, Collation and Transaction logging. etc ?

Kind Regards,

AWT

[krowczynski · Accepted solution]

Maybe this can help you.

MCP, VCP

[AlbertWT]

Thanks Krow, that was quick and right what i want.

Cheers.

Kind Regards,

AWT

[AlbertWT]

OK, here's the connection summary:

Microsoft SQL Native Client Version 09.00.4035

Data Source Name: dsnVCDB

Data Source Description: DSN for VCenter

Server: MgMtServer\SYSDB

Use Integrated Security: No

Database: VCDB

Language: (Default)

Data Encryption: No

Trust Server Certificate: No

Multiple Active Result Sets(MARS): No

Mirror Server:

Translate Character Data: Yes

Log Long Running Queries: No

Log Driver Statistics: No

Use Regional Settings: No

Use ANSI Quoted Identifiers: Yes

Use ANSI Null, Paddings and Warnings: Yes

username: vclogin --> SQL Auth.

Kind Regards,

AWT