What happens if I put this on a machine with more than 1 physical CPU (I know cores aren't an issue). I assume it will run and I can do this, but it'll only schedule threads to 1 CPU and it's cores (like a kind of throttle). this is what Oracle is doing from what I understand.
Exceeding 1 physical CPU with SQL Server Express
Hot Topic
- Error 8152: "String or binary data would be truncated"
- Sychronization error - MSSQL_REPL22037
- Auto Create trigger after re-initialization completed
- Could anyone attach the AdventureWorksDW to their SQL Server database engine?
- SQL Server 2005 Timeout expired exception
- New Query button -- always prompts for authentication
- DataBase path
- QueryLog to a file
- SQL Server Encryption in MSDE 2000
- Running query in SQL 2005 stored procedure against table on SQL 2000
SQL Server
- Express 2005 / Hardware CPU RAM ?
- SQL 2000 to SQL 2005 works for one 2000 server but not the next
- creating a trace definition file (TDF) via code
- Snapshot agent can not connect to distributor
- table schema changes not being propagated - merge replication
- Error of Microsoft OLE DB Provider for SQL Server
- Execute a task even though a checkpoint file says it has already been executed
- Can't Attach Database using SQL Server Management Studio Express
- DDS- New Concdern
- Catch Error message in Variable?
Exceeding 1 physical CPU with SQL Server Express