operationg system requirement

I am in the process of learning SQL from scratch and figure it would be helpful if I can run a local server and experiment with it as I move along some book reading. I have a few questions regarding the operating system requirement for running a localhost server and hope some of you can answer to my novice questions. Can I setup a server under Windows XP? when I looked thru the documentation it indicated only windows 2000 and other Microsoft server OS will support a SQL server setup. Why then it also indicate XP as compatible? Is it because it's compatible as a client? If I do have to run a server under a different operationg system, what is the best approach for setting up another server on my only PC system along with my XP. Thanks for any answers and comments in advance.

Are you talking about SQL 2005? XP does support SQL 2005, but it depends on which edition you have. See the following link for more information about which edition is supported on which OS. http://www.microsoft.com/sql/prodinfo/sysreqs/default.mspx

|||I'm not completely clear on whether I'm covered for a developer edition
Does "Windows XP with SP 2 or later" mean that the media center edition 2005 should suffice?
|||

Short answer: Yes.

Please see topic "Hardware and Software Requirementse for Installing SQL Server 2005" for more information.

http://msdn2.microsoft.com/en-us/library/ms143506(SQL.90).aspx

|||Short Answer: Thanks
|||so with an athlon 64 X2 dual Core processor 3800+ 2Ghz I should be ordering the
x64 developer version rather than win32? Or would the latter also work (and be compatible with an older processor)
|||

x86 can install on X64 machine, but you should install x64 version if you can.

Operationg System Command (CmdExec) job failing

I have sql 2000 job that has been setup as a "Operating System Command (CmdExec) job. I am logged into the SQL Server as DomainName\SQLAdmin this domain account is part of the Administrator group on the SQL Server that the job in running on. This account has SysAdmin rights and is also starting the MSSQLSERVER Service and SQLSERVERAGENT Service on the same machine.

The job just copies files from one directory to another, here's the code.

D:
cd \MSSQL\BACKUP\AP\AP_Primary
xcopy *.* D:\MSSQL\BACKUP\AP\ /s/y/d

When run as a job, with the owner of the job being DomainName\SQLAdmin the job fails with the following error message: Executed as user: DomainName\SQLAdmin. The process could not be created for step 1 of job 0x822E9AD29DCAAF4196369A46C7FE212A (reason: Access is denied). The step failed.

Here's the weird part if I open a command window on the sql server and run the batch it works fine.

I even tried executing the commands via xp_cmdshell but that didn't work either, I recieved the message: (1 row(s) affected) with the output being NULL and the file was never copied.

Anyone have an idea whats going on?It sounds like there could be multiple reasons for the access denied issue, but an odd one which I just found out about follows:

I was just trying to restore a db and I was receiving an Access denied error. I ended up finding out that some of the parent folders were in 'read only' mode. After I disabled it, everything worked fine.

Good luck,
Hope this helped|||what account is listed as the job owner?|||The account that owns the job, DomainName\SQLAdmin, is also the account that belongs to the Administrator group on the server and Stops and Starts the MSSQLSERVER/SQLSERVERAGENT services. As far as I can tell this account has all the permissions possible.

Also checked permissions on all parent folders none are marked read-only.|||I found a work around but it doesn't explain why my original job failed. What I did was create a batch file with the following code.

D:
cd \MSSQL\BACKUP\AP\AP_Primary
xcopy *.* D:\MSSQL\BACKUP\AP\ /s/y/d

I then stored it on the C: drive and called the batch from within the job and this worked. So anyone have an idea what's going on? I'm sure it's a permissions thing but I can't explain it.

Operation is not allowed while the object is closed (was "Hmmm")

never seen this before, but I keep getting an error > "Operationg is not allowed while the object is closed" I thought maybe I was getting this due to an error in my stored procedure, however the procedure runs fine. Could this be an error in my procedure that it's just not catching? Or is it more likely to be in my VB code? Anyone know in general why this happens? Thanks.Yes this is sounds like an ADO error in your VB code. You are either trying to run a procedure against a closed connection object or you trying to access the data from a recordset object that has not been set or open.