June 2, 2011 at 9:58 am
Ive been working long time whit SQL server, but never really understood some things..
So i guss im a newbie haha..
please can some one explain this to me.
See attached image..
1 Server it has both IIS and SQL
My server: MS 2008 R2 - 64Bit
My SQL: MS 2008 R2 - 64Bit
1. Why are there both 32 and one one called anything = i thing its 64 bit.
I have disable all the things in the 32 bit thing..
Was that smart??
Or if i configure them both, will it give me even better performances, like under DDos attacks and no more connections will there be both 32 bit and 64 bit connections available???
2. Whats the difference in.
SQL server network configuration
and
SQL Native client 10 configuration.
3. i have disable all except TCP/IP
is that okay?
All sites that access the SQL are on same server as SQL.
The only outside connector is me from SQL management studio..
i like to disable all things that are not used, can i disable more things?
Thanks a lot, this will help me a lot i hope some one will be nice and school me a bit in the above 🙂
Thanks
BrownGhost
June 2, 2011 at 10:54 am
Generally speaking, it's best to separate IIS and web pages/application from SQL Server, but I understand that can't always be done.
SQL Server Native Client is a way to connect to SQL Server. There are other ways. You have to configure both things. I recommend searching for both items in MSDN. There's a fair amount of material about both. A lot more than can be covered in a simple forum post.
Disabling "Shared Memory" means that applications on the same server, which you have, have to use TCP/IP to connect to SQL. You'll need to review the effects of that, but usually Shared Memory is the best way to have local applications access the server.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
June 2, 2011 at 11:53 am
thanks ill re enable shared memory..
what about this, i did not see answer for that question?
1. Why are there both 32 and one one called anything = i thing its 64 bit.
I have disable all the things in the 32 bit thing..
Was that smart??
Or if i configure them both, will it give me even better performances, like under DDos attacks and no more connections will there be both 32 bit and 64 bit connections available???
Thanks
BrownGhost
June 3, 2011 at 6:22 am
brownghost (6/2/2011)
thanks ill re enable shared memory..what about this, i did not see answer for that question?
1. Why are there both 32 and one one called anything = i thing its 64 bit.
I have disable all the things in the 32 bit thing..
Was that smart??
Or if i configure them both, will it give me even better performances, like under DDos attacks and no more connections will there be both 32 bit and 64 bit connections available???
I'm afraid I don't understand that question as it's worded. Are you talking about 32-bit vs 64-bit? On what?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
June 3, 2011 at 10:38 am
native client.. look in picture..
why are there 2??
Thanks
BrownGhost
June 6, 2011 at 6:24 am
Because there are 32-bit and 64-bit drivers. Unless you can be certain only one or the other will ever be used, you're probably better off leaving both running.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply