Sql-server – Remove sql server service from windows 7

As per MSDN you can't install SQL Server 2005 Enterprise Edition on Windows XP. It's not supported. It seems that you can install client tools, BOL and some legacy tools, but not the database server engine itself.

So to answer your question: the SQL Server engine has very likely not been installed when you run setup, so neither you can connect to it, nor you can start any SQL Server service.

The actual memory in use won't increase until you actually load data into memory. It's not going to jump to 10GB combined allocated just because that's what you've set max memory to and because your databases are at least that large. It's a max, not a min (and never mind that min doesn't work that way either), and it isn't going to try to guess - before you've run enough queries - which tables / indexes it should load into buffer pool memory.

So yes, it is normal to see a gap in these values. You can probably get much closer to the max values if you pump the buffer pool by issuing a bunch of SELECT * FROM dbo.BiggestTables; on each instance, but it is usually better to let SQL Server allocate the memory as it deems appropriate based on actual usage by your real application. And remember too that max server memory doesn't just cover the buffer pool.

In short, SQL Server is pretty good at memory management; let it do its thing, and worry about adjusting max memory on your various instances when you have an actual performance issue.