May 22, 2015 at 3:24 am
audiocool (5/22/2015)
GilaMonster (5/22/2015)
audiocool (5/22/2015)
is the following service require to turn onSQL Server Analysis Service ?
Are you planning to use it's features? Are you planning to build cubes, do data mining and the like on this server?
If so, then yes (though you probably would be better off using a different server). If not, then no.
I'm not sure what is the build cubes and data mining..
Our SQL server basically used for data exchange purposes (application <-> database)
Then SSAS is probably unnecessary.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 22, 2015 at 8:32 am
Okay dude... you're out of your league, and you need help. You are starting to flail around, doing things that won't help just to do something. There are several people on this thread that have already told you that they can help you out. Please, do yourself and your company a favor... tell your boss that you need help to get this fixed, and bring some of these names to him. Three people trying to help you out here are Microsoft Certified Masters, and others on this thread are seasoned professionals. All are well qualified to help you out. Pick one, submit it to your boss as your preference, and let's get someone in there that can actually fix the problem. As you continue to flail, you're going to end up meddling with something that you shouldn't have, and end up causing more problems.
Please take this seriously. You really need someone that knows what they're doing hands on with your system to figure it out.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
May 22, 2015 at 8:47 am
WayneS (5/22/2015)
Okay dude... you're out of your league, and you need help. You are starting to flail around, doing things that won't help just to do something. There are several people on this thread that have already told you that they can help you out. Please, do yourself and your company a favor... tell your boss that you need help to get this fixed, and bring some of these names to him. Three people trying to help you out here are Microsoft Certified Masters, and others on this thread are seasoned professionals. All are well qualified to help you out. Pick one, submit it to your boss as your preference, and let's get someone in there that can actually fix the problem. As you continue to flail, you're going to end up meddling with something that you shouldn't have, and end up causing more problems.Please take this seriously. You really need someone that knows what they're doing hands on with your system to figure it out.
+1000
May 22, 2015 at 9:40 am
GilaMonster (5/22/2015)
audiocool (5/22/2015)
What is pending:1) McAfee (Can't make any changes as setting is been locked by corporate team. Local IT also can't do anything. Will proceed after received feedback)
And the query tuning, which is most likely where you're going to get the most gains.
+1,000,000,000:-D
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
May 22, 2015 at 9:45 am
GilaMonster (5/22/2015)
Please ask him to make sure that configurations are per the Microsoft KB articleshttps://support.microsoft.com/en-us/kb/2033238 and https://support.microsoft.com/en-us/kb/309422
IMHO - those recommendations are the lowest common denominator if you MUST have AV installed on a SQL box.
AV should never scan any volume containing data and log files. We can throw in there that it shouldn't scan volumes containing backups and traces as well.
Oh and even though they say on-access scan is disabled, I have seen it actively scan (especially McAfee) the database files. Just disabling AV on the server altogether has shown to provide 10-15% bumps in performance (even when configured according to the Microsoft recommendations).
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
May 22, 2015 at 12:32 pm
SQLRNNR (5/22/2015)
GilaMonster (5/22/2015)
Please ask him to make sure that configurations are per the Microsoft KB articleshttps://support.microsoft.com/en-us/kb/2033238 and https://support.microsoft.com/en-us/kb/309422
IMHO - those recommendations are the lowest common denominator if you MUST have AV installed on a SQL box.
AV should never scan any volume containing data and log files. We can throw in there that it shouldn't scan volumes containing backups and traces as well.
Oh and even though they say on-access scan is disabled, I have seen it actively scan (especially McAfee) the database files. Just disabling AV on the server altogether has shown to provide 10-15% bumps in performance (even when configured according to the Microsoft recommendations).
Piling on, the top 1 reason for not allowing RDP onto the SQL Servers is that any decent endpoint security policy will spawn a virus scanner (and more) on any system as you log on to it, the configuration of those may not be in line with MS Best Practices for virus scanners on an SQL Server and often the results are catastrophic.
😎
Echoing the fine advice of Wayne, Gail, Grant, Jeff, Jason and others, it's time to call in the ghost busters!
May 22, 2015 at 12:49 pm
Eirikur Eiriksson (5/22/2015)
Piling on, the top 1 reason for not allowing RDP onto the SQL Servers is that any decent endpoint security policy will spawn a virus scanner (and more) on any system as you log on to it, the configuration of those may not be in line with MS Best Practices for virus scanners on an SQL Server and often the results are catastrophic.
Plus an RDP session can easily consume a GB of memory idle. More if anything's actually being run.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 23, 2015 at 2:34 pm
This thread has become a laundry list of worst practices!! 🙂
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
May 23, 2015 at 2:46 pm
TheSQLGuru (5/23/2015)
This thread has become a laundry list of worst practices!! 🙂
That by itself presents an opportunity, care to do a write up?
😎
May 24, 2015 at 6:59 pm
HI Grant,
This is the current usage of the server since 2 days + after changes made (change OS page file, cost of threshold 5 -> 40, disable scan on mdf, ldf)
Oh ya, you guys is always talking about RDP. What is the RDP you guys talking about ?
Is that Remote desktop connection ? If yes, we all login to SQL Server via Remote Desktop Connection.
If this is not recommended, what will the client use to remote in.
May 24, 2015 at 9:43 pm
audiocool (5/24/2015)
Oh ya, you guys is always talking about RDP. What is the RDP you guys talking about ?Is that Remote desktop connection ? If yes, we all login to SQL Server via Remote Desktop Connection.
If this is not recommended, what will the client use to remote in.
Yes, RDP is Remote Desktop Protocol / Remote Desktop Connection and it is should be avoided if possible as it can consume considerable amount of the server's resources etc.. As almost anything can be done on the server without RDP'ing on to it, my question is why does the client need to do it?
😎
May 25, 2015 at 12:41 am
only a few of IT personnel will have authorize to access it. Access to server recently is to make changes on McAfee and check some of the message in Event Viewer.
If this is not recommended then which tools is good to use ? I know a few VNC Viewer, Ultrac VNC..
May 25, 2015 at 1:21 am
audiocool (5/24/2015)
Is that Remote desktop connection ? If yes, we all login to SQL Server via Remote Desktop Connection.
Well there's part of your problem.
If this is not recommended, what will the client use to remote in.
Err, nothing. Remoting in to a production server should be a rare event, not an everyday occurrence. SQL can be managed remotely, many things can be done remotely. The administrators (and only the administrators) should remote in only when they absolutely need to
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 25, 2015 at 7:53 am
GilaMonster (5/25/2015)
audiocool (5/24/2015)
Is that Remote desktop connection ? If yes, we all login to SQL Server via Remote Desktop Connection.Well there's part of your problem.
If this is not recommended, what will the client use to remote in.
Err, nothing. Remoting in to a production server should be a rare event, not an everyday occurrence. SQL can be managed remotely, many things can be done remotely. The administrators (and only the administrators) should remote in only when they absolutely need to
+1
Event logs, for example, can be read from another machine without using RDP to log in.
May 25, 2015 at 9:57 am
Eirikur Eiriksson (5/23/2015)
TheSQLGuru (5/23/2015)
This thread has become a laundry list of worst practices!! 🙂That by itself presents an opportunity, care to do a write up?
😎
Nope, sorry. I don't like to create material. I don't blog or write books or articles or maintain a website for my consulting business. Hell, I don't even keep my resume up to date! 😀 Even the almost 300 sessions I have presented at SQL Saturday events have mostly been material that others graciously let me borrow.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 15 posts - 91 through 105 (of 107 total)
You must be logged in to reply to this topic. Login to reply