Showing posts with label requirements. Show all posts
Showing posts with label requirements. Show all posts

Friday, March 23, 2012

PC Hardware requirements for SQL 2005 Standard Edition

Hello,

I'm wondering if it is possible to install SQL2005 standard edition on a standard dual core pc with Win XP Pro SP2 OS.

Kindly advice.

Regards

Andy

That should be fine.

As a first part of the install process, a program will execute that will verify that the hardware and software environment will support SQL Server 2005.

To check the requirements, see this resource:

SQL Server 2005 Installation Requirements (Hardware/Software)
http://msdn2.microsoft.com/en-us/library/ms143506.aspx

|||Thank you, that should save me some cash from buying a server unit.

Wednesday, March 21, 2012

Pausing Log Shipping Plans

We are doing an IP Restructuring on our DR site over the weekend due to some business and management requirements.I actually have 2 questions. I have implemented log shipping plans for our databases. Which means I will have to pause (disable) my log shipping plans while this is being done and resume (re-enable) after everything is comlete.

Any insights on what else I need to do apart from these?

My second question is this. I am generating transaction log backups every 15 minutes and is averaging at 350MB (this much data every 15 minutes - not to mention that I've got around 40+ databases, all configured for log shipping just for this instance alone). My alert threshold is 45 minutes. My log shipping plan for one database starts failing probably because 15 minutes is not enough to transfer 300+MB-sized backup file over a WAN locate across the globe on a not-so-high bandwidth and restore it to the destination. Any recommendations on this apart from increasing the threshold? Your assistance is highly appreciated

Log shipping should not be affected by changing the IP addresses unless you change ones targetted directly by the log shipping jobs. For the WAN case, you can consider adding a step to compress the transaction log backups prior to copying them over the network. This typically improves the end-toend throughput over a WAN.

Regards,

Matt Hollingsworth

Sr. Program Manager

SQL Server High Availability

|||

Hi Matt,

Thanks for your reply. Actually, we will be changing the IPs of the destination servers Sad You were mentioning compressing the transaction log backups prior to copying them over the network. I am using the Database maintenance plans to define my log shipping plans. The way I see it, the copy job does a "pull" method - the destination server is the one initiating the job. How do you insert a step to compress the transaction log backup files in the database maintenance plans? I am only allowed to use "Microsoft supported" procedures as per company policy

sql

Wednesday, March 7, 2012

Password does not meet Windows policy requirements 2005

I have been given the task to see if our software will work against SQL
Server 2005:-
XP Pro installed on a Virtual PC
SQL Server 2005 Standard Edition Installed
Mixed mode Security
Check policy set to off
Installation of 2005 was successful and no error reported in the logs.
Now the fun started hen attempting to install our software, using the SA
account (we have also created additional SQL logins too but still have the
same problem) it gets as far as creating the various databases but when
attempting to create tables it receives the following error:-
Create Table failed
SQL-DMO error: 15118 [Microsoft][ODBC SQL Server Driver][SQL Server]
Password validation failed.The password does not meet Windows policy
requirements because it is not complex enough
The password we are using meets the criteria for creating passwords and I
have also checked Windows Security Settings and the Passord Policy 'Password
must meet complexity requirements' is disabled
If you need any additional information please let me know.
Many thanks
PaulHi Paul,
make sure that there is o domain policy activated which forces secure
passwords.
HTH, jens Suessmeyer.|||Jens,
Thank you for your reply the domain policy is not currently active
Paul
"Jens" wrote:
> Hi Paul,
> make sure that there is o domain policy activated which forces secure
> passwords.
> HTH, jens Suessmeyer.
>