From fuller.artful at gmail.com Wed Apr 11 16:58:16 2018 From: fuller.artful at gmail.com (Arthur Fuller) Date: Wed, 11 Apr 2018 17:58:16 -0400 Subject: [dba-SQLServer] [AccessD] Bulk insert and table names In-Reply-To: References: <015e01c804f4$0851f7a0$6c7aa8c0@M90> <015f01c804fc$ba890230$6c7aa8c0@M90> Message-ID: Long ago, there was a SQL equivalent of a tongue twister. I'll see if I can recall it. Tables: Select ID autoincrement Select varchar(100) From ID autoincrement From varchar(100) Already, you can see where this is going. Parse this, you motherf**ker! SELECT SELECT.Select, FROM.From INNER JOIN FROM ON SELECT.id = FROM.ID ORDER BY SELECT.Select Arthur the Asinine, son of Douglas the Douche (or was it the Duke?) On Tue, Oct 2, 2007 at 11:56 AM, Francisco Tapia wrote: > The thing is that if you bracket your table names, you're allowed to use > them, prefixing your table names with something simple such as tblOR or > tblIN would have clearly avoided the problem you faced. Similarly with > indexes, you've found a great way to keep them unique by including the > tablename in the index. From jnatola at hotmail.com Tue Apr 24 09:23:32 2018 From: jnatola at hotmail.com (J- P) Date: Tue, 24 Apr 2018 14:23:32 +0000 Subject: [dba-SQLServer] sql performance monitoring Message-ID: Hi all, Client decided to upgrade from sql express to full sql, the database runs in 2000 compatibility mode, so it is currently sql2008 running on server 2012. Its a hyperV guest with 1 vcpu and 8gb of ram (5 gb allocated to sql) The database is small (~2gb) it has an Access front end and there are about 40 concurrent users, on multiple occasions the server slows down and the only recourse is restarting sql service. I have been tasked with "finding out what is wrong" , I'm not a sql admin but having been a network admin for almost 20 years , and having setup numerous commercial sql dbs (Great Plains, Share point, Sage) on much inferior hardware , with much larger databases I have to believe that the problem lies in the DB/FE configuration itself. Of course the in-house "dba" refuses to believe that, and has always shot me down when suggesting to get a real dba to come to assess the code and make it more efficient, (IMO it should not 5 to 10 seconds to run a query). I have setup some perf counters based on what I have read, in addition I would like to get a tool(s) specifically made for sql that pinpoints where the issue(s) are. I have budget so it does not have to be free, the two I have been looking at is Solarwinds and ManageEngine Does anyone have a preference or suggestion? TIA From fhtapia at gmail.com Tue Apr 24 10:01:39 2018 From: fhtapia at gmail.com (fhtapia at gmail.com) Date: Tue, 24 Apr 2018 15:01:39 +0000 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: Message-ID: I've never used ManageEngine, but I've used soalrwinds, Redgate and Idera... I believe Idera has a free tool you can begin with, it'll run over the DB and provide a result of the poor performing queries. I think it's a mistake to run the database in the lower compatibility mode unless there is a feature the current developer is supporting, in which case, we are in Sql Server 2012, and he should support the latest version, as bugs with the older compatibility mode will stop functioning. There are many faster better features in the latest version of sql server, plus in 2012 you can fully make use of RSCI.. ( https://littlekendra.com/2016/02/18/how-to-choose-rcsi-snapshot-isolation-levels/ ) good luck! Francisco Tapia On Tue, Apr 24, 2018 at 7:30 AM J- P wrote: > Hi all, > > > Client decided to upgrade from sql express to full sql, the database runs > in 2000 compatibility mode, so it is currently sql2008 running on server > 2012. > > > Its a hyperV guest with 1 vcpu and 8gb of ram (5 gb allocated to sql) > > > The database is small (~2gb) it has an Access front end and there are > about 40 concurrent users, on multiple occasions the server slows down and > the only recourse is restarting sql service. > > > I have been tasked with "finding out what is wrong" , I'm not a sql admin > but having been a network admin for almost 20 years , and having setup > numerous commercial sql dbs (Great Plains, Share point, Sage) on much > inferior hardware , with much larger databases I have to believe that the > problem lies in the DB/FE configuration itself. > > > Of course the in-house "dba" refuses to believe that, and has always shot > me down when suggesting to get a real dba to come to assess the code and > make it more efficient, (IMO it should not 5 to 10 seconds to run a query). > > > I have setup some perf counters based on what I have read, in addition I > would like to get a tool(s) specifically made for sql that pinpoints where > the issue(s) are. > > > I have budget so it does not have to be free, the two I have been looking > at is Solarwinds and ManageEngine > > > > Does anyone have a preference or suggestion? > > > TIA > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > From jnatola at hotmail.com Mon Apr 23 10:20:00 2018 From: jnatola at hotmail.com (J- P) Date: Mon, 23 Apr 2018 15:20:00 +0000 Subject: [dba-SQLServer] Sql monitoring Message-ID: Hi all, Client decided to upgrade from sql express to full sql, the database runs in 2000 compatibility mode, so it is currently sql2008 running on server 2012. Its a hyperV guest with 1 vcpu and 8gb of ram (5 gb allocated to sql) The database is small (~2gb) it has an Access front end and there are about 40 concurrent users, on multiple occasions the server slows down and the only recourse is restarting sql service. I have been tasked with "finding out what is wrong" , I'm not a sql admin but having been a network admin for almost 20 years , and having setup numerous commercial sql dbs (Great Plains, Share point, Sage) on much inferior hardware , with much larger databases I have to believe that the problem lies in the DB/FE configuration itself. Of course the in-house "dba" refuses to believe that, and has always shot me down when suggesting to get a real dba to come to assess the code and make it more efficient, (IMO it should not 5 to 10 seconds to run a query). I have setup some perf counters based on what I have read, in addition I would like to get a tools specifically made for sql that pinpoints where the issue(s) are. I have budget so it does not have to be free, the two I have been looking at is Solarwinds and ManageEngine Does anyone have a preference or suggestion? From jnatola at hotmail.com Mon Apr 23 13:59:43 2018 From: jnatola at hotmail.com (J- P) Date: Mon, 23 Apr 2018 18:59:43 +0000 Subject: [dba-SQLServer] SQL monitoring Message-ID: Hi all, Client decided to upgrade from sql express to full sql, the database runs in 2000 compatibility mode, so it is currently sql2008 running on server 2012. Its a hyperV guest with 1 vcpu and 8gb of ram (5 gb allocated to sql) The database is small (~2gb) it has an Access front end and there are about 40 concurrent users, on multiple occasions the server slows down and the only recourse is restarting sql service. I have been tasked with "finding out what is wrong" , I'm not a sql admin but having been a network admin for almost 20 years , and having setup numerous commercial sql dbs (Great Plains, Share point, Sage) on much inferior hardware , with much larger databases I have to believe that the problem lies in the DB/FE configuration itself. Of course the in-house "dba" refuses to believe that, and has always shot me down when suggesting to get a real dba to come to assess the code and make it more efficient, (IMO it should not 5 to 10 seconds to run a query). I have setup some perf counters based on what I have read, in addition I would like to get a tools specifically made for sql that pinpoints where the issue(s) are. I have budget so it does not have to be free, the two I have been looking at is Solarwinds and ManageEngine Does anyone have a preference or suggestion? TIA From jnatola at hotmail.com Tue Apr 24 11:11:10 2018 From: jnatola at hotmail.com (J- P) Date: Tue, 24 Apr 2018 16:11:10 +0000 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: , Message-ID: That is part of the issue the database started as Access 95 or 97 (before I was around) the client , not willing to hire an actual programmer would use an in-house employee to add things to the Access DB, fast forward 10 years (2006 ish) its now up to the 4th "access programmer", and between him and the previous IT vendor decide, time to split Access to an sql back-end (sql express 2000). Fast forward its 2014/15 things are slowly added to the database, company grows some, more employees/users etc.. , I take over the IT services with the stipulation that the database is outside the contract- Still running on sql express , hardware / software refresh time the programmer states its time to upgrade to full sql as express has the one GB ram limit- This gets rejected due to the cost- As more bells and whistles are added things progressively get worse- finally this year they decide they have to bit the bullet and pay for SQL, and as its a virtualized environment they have to buy the 4 core model. During the upgrade I deploy a sql 2012, restore the DB the database launches, however, many, many, functions do not work- I am requested to deploy 2008 in 2k compatibility mode. So now it is running sql 08 on server 2012 as HyperV guest on a raid10 ,8GB of ram and I see ZERO performance improvement- mind you express was running on a PowerEdge 860 with a Pentium cpu. Thanks, ________________________________ From: dba-SQLServer on behalf of fhtapia at gmail.com Sent: Tuesday, April 24, 2018 11:01 AM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring I've never used ManageEngine, but I've used soalrwinds, Redgate and Idera... I believe Idera has a free tool you can begin with, it'll run over the DB and provide a result of the poor performing queries. I think it's a mistake to run the database in the lower compatibility mode unless there is a feature the current developer is supporting, in which case, we are in Sql Server 2012, and he should support the latest version, as bugs with the older compatibility mode will stop functioning. There are many faster better features in the latest version of sql server, plus in 2012 you can fully make use of RSCI.. ( https://littlekendra.com/2016/02/18/how-to-choose-rcsi-snapshot-isolation-levels/ [https://littlekendra.com/wp-content/uploads/2016/02/reads-vs-writes-RCSI.png] How to Choose Between Snapshot and RCSI - by Kendra Little littlekendra.com SQL Server offers two flavors of optimistic locking for traditional disk-based tables: Read Committed Snapshot Isolation (RCSI), and Snapshot Isolation. They are each great tools to reduce blocking and make applications faster, particularly in databases that have lots of tiny reads and writes that ... ) good luck! Francisco Tapia On Tue, Apr 24, 2018 at 7:30 AM J- P wrote: > Hi all, > > > Client decided to upgrade from sql express to full sql, the database runs > in 2000 compatibility mode, so it is currently sql2008 running on server > 2012. > > > Its a hyperV guest with 1 vcpu and 8gb of ram (5 gb allocated to sql) > > > The database is small (~2gb) it has an Access front end and there are > about 40 concurrent users, on multiple occasions the server slows down and > the only recourse is restarting sql service. > > > I have been tasked with "finding out what is wrong" , I'm not a sql admin > but having been a network admin for almost 20 years , and having setup > numerous commercial sql dbs (Great Plains, Share point, Sage) on much > inferior hardware , with much larger databases I have to believe that the > problem lies in the DB/FE configuration itself. > > > Of course the in-house "dba" refuses to believe that, and has always shot > me down when suggesting to get a real dba to come to assess the code and > make it more efficient, (IMO it should not 5 to 10 seconds to run a query). > > > I have setup some perf counters based on what I have read, in addition I > would like to get a tool(s) specifically made for sql that pinpoints where > the issue(s) are. > > > I have budget so it does not have to be free, the two I have been looking > at is Solarwinds and ManageEngine > > > > Does anyone have a preference or suggestion? > > > TIA > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From scott.marcus at tsstech.com Tue Apr 24 12:22:49 2018 From: scott.marcus at tsstech.com (Scott Marcus) Date: Tue, 24 Apr 2018 13:22:49 -0400 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: , Message-ID: Here are areas I would check... How many records are shown on a form? Showing a table on a form (and/or multi join tables in a grid) can easily slow down the application. The Front End (Access DB) may be the culprit. If all the processing happens on the FE you will need to rewrite queries so that processing happens on the server and only the data needed is sent to the client. Does the front end have a lot of drop down lookup combo boxes? You might need to limit this (or at least delay when those drop downs are loaded). How well normalized is the data? How about indexes on those tables to speed up filtering. You could have 100's of data requests on any given form that individually are not slow but when you add them up it could amount to major wait time. Scott Marcus -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of J- P Sent: Tuesday, April 24, 2018 12:11 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring That is part of the issue the database started as Access 95 or 97 (before I was around) the client , not willing to hire an actual programmer would use an in-house employee to add things to the Access DB, fast forward 10 years (2006 ish) its now up to the 4th "access programmer", and between him and the previous IT vendor decide, time to split Access to an sql back-end (sql express 2000). Fast forward its 2014/15 things are slowly added to the database, company grows some, more employees/users etc.. , I take over the IT services with the stipulation that the database is outside the contract- Still running on sql express , hardware / software refresh time the programmer states its time to upgrade to full sql as express has the one GB ram limit- This gets rejected due to the cost- As more bells and whistles are added things progressively get worse- finally this year they decide they have to bit the bullet and pay for SQL, and as its a virtualized environment they have to buy the 4 core model. During the upgrade I deploy a sql 2012, restore the DB the database launches, however, many, many, functions do not work- I am requested to deploy 2008 in 2k compatibility mode. So now it is running sql 08 on server 2012 as HyperV guest on a raid10 ,8GB of ram and I see ZERO performance improvement- mind you express was running on a PowerEdge 860 with a Pentium cpu. Thanks, ________________________________ From: dba-SQLServer on behalf of fhtapia at gmail.com Sent: Tuesday, April 24, 2018 11:01 AM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring I've never used ManageEngine, but I've used soalrwinds, Redgate and Idera... I believe Idera has a free tool you can begin with, it'll run over the DB and provide a result of the poor performing queries. I think it's a mistake to run the database in the lower compatibility mode unless there is a feature the current developer is supporting, in which case, we are in Sql Server 2012, and he should support the latest version, as bugs with the older compatibility mode will stop functioning. There are many faster better features in the latest version of sql server, plus in 2012 you can fully make use of RSCI.. ( https://littlekendra.com/2016/02/18/how-to-choose-rcsi-snapshot-isolation-levels/ [https://littlekendra.com/wp-content/uploads/2016/02/reads-vs-writes-RCSI.png] How to Choose Between Snapshot and RCSI - by Kendra Little littlekendra.com SQL Server offers two flavors of optimistic locking for traditional disk-based tables: Read Committed Snapshot Isolation (RCSI), and Snapshot Isolation. They are each great tools to reduce blocking and make applications faster, particularly in databases that have lots of tiny reads and writes that ... ) good luck! Francisco Tapia On Tue, Apr 24, 2018 at 7:30 AM J- P wrote: > Hi all, > > > Client decided to upgrade from sql express to full sql, the database > runs in 2000 compatibility mode, so it is currently sql2008 running on > server 2012. > > > Its a hyperV guest with 1 vcpu and 8gb of ram (5 gb allocated to sql) > > > The database is small (~2gb) it has an Access front end and there are > about 40 concurrent users, on multiple occasions the server slows down > and the only recourse is restarting sql service. > > > I have been tasked with "finding out what is wrong" , I'm not a sql > admin but having been a network admin for almost 20 years , and having > setup numerous commercial sql dbs (Great Plains, Share point, Sage) on > much inferior hardware , with much larger databases I have to believe > that the problem lies in the DB/FE configuration itself. > > > Of course the in-house "dba" refuses to believe that, and has always > shot me down when suggesting to get a real dba to come to assess the > code and make it more efficient, (IMO it should not 5 to 10 seconds to run a query). > > > I have setup some perf counters based on what I have read, in > addition I would like to get a tool(s) specifically made for sql that > pinpoints where the issue(s) are. > > > I have budget so it does not have to be free, the two I have been > looking at is Solarwinds and ManageEngine > > > > Does anyone have a preference or suggestion? > > > TIA > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com NOTICE: This electronic mail transmission is for the use of the named individual or entity to which it is directed and may contain information that is privileged or confidential. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of any information contained herein is prohibited. If you have received this electronic mail transmission in error, delete it from your system without copying or forwarding it, and notify the sender of the error by replying via email or calling TSS Technologies at (513) 772-7000, so that our address record can be corrected. Any information included in this email is provided on an ?as is? and ?where as? basis, and TSS Technologies makes no representations or warranties of any kind with respect to the completeness or accuracy of the information contained in this email. From fuller.artful at gmail.com Tue Apr 24 12:47:57 2018 From: fuller.artful at gmail.com (Arthur Fuller) Date: Tue, 24 Apr 2018 13:47:57 -0400 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: Message-ID: As Scott said, the first thing to look at is your queries. First, find all data- and row-sources that begin with "SELECT" and replace those with named queries. Next, convert all these named queries into SQL Views. (The reason for this is that when Access uses a SELECT ... WHERE it first requests all the data, then filters it on the local machine. When Access uses a SQL View, the data filtering occurs on the server, not the local app. With a lot of users, the difference can be dramatic. If your forms contain tabs, then use Colby''s JIT form-style to postpone the data-loads until they are needed. Another technique, especially good for frequently-sed combo- and list-boxes, is to declare a global variable for each list and populate them all at once. That way they live in RAM and no round trips are required. That can result in significant savings, too. Finally, you could convert some of your queries to Pass-Through-Queries. They aren't difficult, but if you haven't used them, you may have to do some reading up on them first. ? Arthur From accessd at shaw.ca Tue Apr 24 13:42:40 2018 From: accessd at shaw.ca (Jim Lawrence) Date: Tue, 24 Apr 2018 12:42:40 -0600 (MDT) Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: Message-ID: <1945278250.514667493.1524595360441.JavaMail.zimbra@shaw.ca> The world of computer product developement never changes. ;-) The search for the holy grail...the perfectly tailored application with little or no cost. Jim ----- Original Message ----- From: "J- P" To: "Discussion concerning MS SQL Server" Sent: Tuesday, April 24, 2018 9:11:10 AM Subject: Re: [dba-SQLServer] sql performance monitoring That is part of the issue the database started as Access 95 or 97 (before I was around) the client , not willing to hire an actual programmer would use an in-house employee to add things to the Access DB, fast forward 10 years (2006 ish) its now up to the 4th "access programmer", and between him and the previous IT vendor decide, time to split Access to an sql back-end (sql express 2000). Fast forward its 2014/15 things are slowly added to the database, company grows some, more employees/users etc.. , I take over the IT services with the stipulation that the database is outside the contract- Still running on sql express , hardware / software refresh time the programmer states its time to upgrade to full sql as express has the one GB ram limit- This gets rejected due to the cost- As more bells and whistles are added things progressively get worse- finally this year they decide they have to bit the bullet and pay for SQL, and as its a virtualized environment they have to buy the 4 core model. During the upgrade I deploy a sql 2012, restore the DB the database launches, however, many, many, functions do not work- I am requested to deploy 2008 in 2k compatibility mode. So now it is running sql 08 on server 2012 as HyperV guest on a raid10 ,8GB of ram and I see ZERO performance improvement- mind you express was running on a PowerEdge 860 with a Pentium cpu. Thanks, ________________________________ From: dba-SQLServer on behalf of fhtapia at gmail.com Sent: Tuesday, April 24, 2018 11:01 AM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring I've never used ManageEngine, but I've used soalrwinds, Redgate and Idera... I believe Idera has a free tool you can begin with, it'll run over the DB and provide a result of the poor performing queries. I think it's a mistake to run the database in the lower compatibility mode unless there is a feature the current developer is supporting, in which case, we are in Sql Server 2012, and he should support the latest version, as bugs with the older compatibility mode will stop functioning. There are many faster better features in the latest version of sql server, plus in 2012 you can fully make use of RSCI.. ( https://littlekendra.com/2016/02/18/how-to-choose-rcsi-snapshot-isolation-levels/ [https://littlekendra.com/wp-content/uploads/2016/02/reads-vs-writes-RCSI.png] How to Choose Between Snapshot and RCSI - by Kendra Little littlekendra.com SQL Server offers two flavors of optimistic locking for traditional disk-based tables: Read Committed Snapshot Isolation (RCSI), and Snapshot Isolation. They are each great tools to reduce blocking and make applications faster, particularly in databases that have lots of tiny reads and writes that ... ) good luck! Francisco Tapia On Tue, Apr 24, 2018 at 7:30 AM J- P wrote: > Hi all, > > > Client decided to upgrade from sql express to full sql, the database runs > in 2000 compatibility mode, so it is currently sql2008 running on server > 2012. > > > Its a hyperV guest with 1 vcpu and 8gb of ram (5 gb allocated to sql) > > > The database is small (~2gb) it has an Access front end and there are > about 40 concurrent users, on multiple occasions the server slows down and > the only recourse is restarting sql service. > > > I have been tasked with "finding out what is wrong" , I'm not a sql admin > but having been a network admin for almost 20 years , and having setup > numerous commercial sql dbs (Great Plains, Share point, Sage) on much > inferior hardware , with much larger databases I have to believe that the > problem lies in the DB/FE configuration itself. > > > Of course the in-house "dba" refuses to believe that, and has always shot > me down when suggesting to get a real dba to come to assess the code and > make it more efficient, (IMO it should not 5 to 10 seconds to run a query). > > > I have setup some perf counters based on what I have read, in addition I > would like to get a tool(s) specifically made for sql that pinpoints where > the issue(s) are. > > > I have budget so it does not have to be free, the two I have been looking > at is Solarwinds and ManageEngine > > > > Does anyone have a preference or suggestion? > > > TIA > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From newsgrps at dalyn.co.nz Tue Apr 24 15:40:04 2018 From: newsgrps at dalyn.co.nz (David Emerson) Date: Wed, 25 Apr 2018 08:40:04 +1200 Subject: [dba-SQLServer] SPAM: Re: sql performance monitoring In-Reply-To: References: Message-ID: <000c01d3dc0c$6cf68590$46e390b0$@dalyn.co.nz> I have a related question which may add to the options. I have a report that has multiple sub reports (up to 40) I am currently using Passthrough queries which get data from stored procedures. We are hitting Out Of Memory errors. If I convert the stored procedures to save the records to SQL tables, link the tables to my Access front end, and use the tables for my reports, will this take up less memory than getting the records via a passthrough query? Regards David Emerson Dalyn Software Ltd Wellington, New Zealand -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller Sent: Wednesday, 25 April 2018 5:48 a.m. To: Discussion concerning MS SQL Server Subject: SPAM: Re: [dba-SQLServer] sql performance monitoring As Scott said, the first thing to look at is your queries. First, find all data- and row-sources that begin with "SELECT" and replace those with named queries. Next, convert all these named queries into SQL Views. (The reason for this is that when Access uses a SELECT ... WHERE it first requests all the data, then filters it on the local machine. When Access uses a SQL View, the data filtering occurs on the server, not the local app. With a lot of users, the difference can be dramatic. If your forms contain tabs, then use Colby''s JIT form-style to postpone the data-loads until they are needed. Another technique, especially good for frequently-sed combo- and list-boxes, is to declare a global variable for each list and populate them all at once. That way they live in RAM and no round trips are required. That can result in significant savings, too. Finally, you could convert some of your queries to Pass-Through-Queries. They aren't difficult, but if you haven't used them, you may have to do some reading up on them first. ? Arthur _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From fhtapia at gmail.com Tue Apr 24 16:24:57 2018 From: fhtapia at gmail.com (fhtapia at gmail.com) Date: Tue, 24 Apr 2018 21:24:57 +0000 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: Message-ID: When you say many functions, do you mean from the Access db? Another thing. Were they vm disk set as real disks or vhd? On Tue, Apr 24, 2018 at 9:16 AM J- P wrote: > That is part of the issue the database started as Access 95 or 97 (before > I was around) the client , not willing to hire an actual programmer would > use an in-house employee to add things to the Access DB, fast forward 10 > years (2006 ish) its now up to the 4th "access programmer", and between him > and the previous IT vendor decide, time to split Access to an sql back-end > (sql express 2000). > > > Fast forward its 2014/15 things are slowly added to the database, company > grows some, more employees/users etc.. , I take over the IT services with > the stipulation that the database is outside the contract- > > Still running on sql express , hardware / software refresh time the > programmer states its time to upgrade to full sql as express has the one GB > ram limit- > > This gets rejected due to the cost- > > > As more bells and whistles are added things progressively get worse- > finally this year they decide they have to bit the bullet and pay for SQL, > and as its a virtualized environment they have to buy the 4 core model. > > > During the upgrade I deploy a sql 2012, restore the DB the database > launches, however, many, many, functions do not work- I am requested to > deploy 2008 in 2k compatibility mode. So now it is running sql 08 on > server 2012 as HyperV guest on a raid10 ,8GB of ram and I see ZERO > performance improvement- mind you express was running on a PowerEdge 860 > with a Pentium cpu. > > > > Thanks, > > > > ________________________________ > From: dba-SQLServer on > behalf of fhtapia at gmail.com > Sent: Tuesday, April 24, 2018 11:01 AM > To: Discussion concerning MS SQL Server > Subject: Re: [dba-SQLServer] sql performance monitoring > > I've never used ManageEngine, but I've used soalrwinds, Redgate and > Idera... I believe Idera has a free tool you can begin with, it'll run over > the DB and provide a result of the poor performing queries. > > I think it's a mistake to run the database in the lower compatibility mode > unless there is a feature the current developer is supporting, in which > case, we are in Sql Server 2012, and he should support the latest version, > as bugs with the older compatibility mode will stop functioning. > > There are many faster better features in the latest version of sql server, > plus in 2012 you can fully make use of RSCI.. ( > > https://littlekendra.com/2016/02/18/how-to-choose-rcsi-snapshot-isolation-levels/ > [ > https://littlekendra.com/wp-content/uploads/2016/02/reads-vs-writes-RCSI.png > ]< > https://littlekendra.com/2016/02/18/how-to-choose-rcsi-snapshot-isolation-levels/ > > > > How to Choose Between Snapshot and RCSI - by Kendra Little< > https://littlekendra.com/2016/02/18/how-to-choose-rcsi-snapshot-isolation-levels/ > > > littlekendra.com > SQL Server offers two flavors of optimistic locking for traditional > disk-based tables: Read Committed Snapshot Isolation (RCSI), and Snapshot > Isolation. They are each great tools to reduce blocking and make > applications faster, particularly in databases that have lots of tiny reads > and writes that ... > > > > ) > > good luck! > Francisco Tapia > > On Tue, Apr 24, 2018 at 7:30 AM J- P wrote: > > > Hi all, > > > > > > Client decided to upgrade from sql express to full sql, the database runs > > in 2000 compatibility mode, so it is currently sql2008 running on server > > 2012. > > > > > > Its a hyperV guest with 1 vcpu and 8gb of ram (5 gb allocated to sql) > > > > > > The database is small (~2gb) it has an Access front end and there are > > about 40 concurrent users, on multiple occasions the server slows down > and > > the only recourse is restarting sql service. > > > > > > I have been tasked with "finding out what is wrong" , I'm not a sql admin > > but having been a network admin for almost 20 years , and having setup > > numerous commercial sql dbs (Great Plains, Share point, Sage) on much > > inferior hardware , with much larger databases I have to believe that the > > problem lies in the DB/FE configuration itself. > > > > > > Of course the in-house "dba" refuses to believe that, and has always shot > > me down when suggesting to get a real dba to come to assess the code and > > make it more efficient, (IMO it should not 5 to 10 seconds to run a > query). > > > > > > I have setup some perf counters based on what I have read, in addition I > > would like to get a tool(s) specifically made for sql that pinpoints > where > > the issue(s) are. > > > > > > I have budget so it does not have to be free, the two I have been looking > > at is Solarwinds and ManageEngine > > > > > > > > Does anyone have a preference or suggestion? > > > > > > TIA > > > > > > _______________________________________________ > > dba-SQLServer mailing list > > dba-SQLServer at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > http://www.databaseadvisors.com > > > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > From jnatola at hotmail.com Tue Apr 24 18:53:06 2018 From: jnatola at hotmail.com (J- P) Date: Tue, 24 Apr 2018 23:53:06 +0000 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: , Message-ID: Correct, Access functions- one thing i have always noted even when it was on the physical server is that the when ever you open any job , for example "Joe Blow reception " You open the job and lets say i want to print/preview proposal, or what equipment is going on the job- ALWAYS at the bottom of the screen in access it says "calculating..................." then it opens- 5,10 even 15 seconds on the average- when things get bad it can take 20-30 or more, or it will crash Access completely - That's when I get the infamous email or text "Access is acting up" or "We can't work" then I login , or tell them to login to the server and "restart the sql service" then everything returns to normal , at least by there standards And when i login the server (before restarting it ) sql maybe at 2gb cpu at like 5% The hyperv disk is Fixed VHDX Jean-Paul Natola ________________________________ From: dba-SQLServer on behalf of fhtapia at gmail.com Sent: Tuesday, April 24, 2018 5:24 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring From accessd at shaw.ca Wed Apr 25 11:58:50 2018 From: accessd at shaw.ca (Jim Lawrence) Date: Wed, 25 Apr 2018 10:58:50 -0600 (MDT) Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: Message-ID: <1386855149.517584144.1524675530610.JavaMail.zimbra@shaw.ca> Why does the SQL service stop? Jim ----- Original Message ----- From: "J- P" To: "Discussion concerning MS SQL Server" Sent: Tuesday, April 24, 2018 4:53:06 PM Subject: Re: [dba-SQLServer] sql performance monitoring Correct, Access functions- one thing i have always noted even when it was on the physical server is that the when ever you open any job , for example "Joe Blow reception " You open the job and lets say i want to print/preview proposal, or what equipment is going on the job- ALWAYS at the bottom of the screen in access it says "calculating..................." then it opens- 5,10 even 15 seconds on the average- when things get bad it can take 20-30 or more, or it will crash Access completely - That's when I get the infamous email or text "Access is acting up" or "We can't work" then I login , or tell them to login to the server and "restart the sql service" then everything returns to normal , at least by there standards And when i login the server (before restarting it ) sql maybe at 2gb cpu at like 5% The hyperv disk is Fixed VHDX Jean-Paul Natola ________________________________ From: dba-SQLServer on behalf of fhtapia at gmail.com Sent: Tuesday, April 24, 2018 5:24 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From fuller.artful at gmail.com Wed Apr 25 12:11:16 2018 From: fuller.artful at gmail.com (Arthur Fuller) Date: Wed, 25 Apr 2018 13:11:16 -0400 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: <1386855149.517584144.1524675530610.JavaMail.zimbra@shaw.ca> References: <1386855149.517584144.1524675530610.JavaMail.zimbra@shaw.ca> Message-ID: One other thing concerning Access functions, including UDFs. Many Access functions have SQL equivalents, and most UDFs can be ported to SQL. Performance gains may not be dramatic regarding UDFs, however. Also, has it been considered that the big problem might be the VM? It might be useful to experiment with a dedicated server rather than a VM, on a weekend or sometime when nobody's using the system. Hardware is so inexpensive now that the performance penalty incurred by the VM software may not be worth it. A.? From jnatola at hotmail.com Wed Apr 25 12:26:32 2018 From: jnatola at hotmail.com (J- P) Date: Wed, 25 Apr 2018 17:26:32 +0000 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: <1386855149.517584144.1524675530610.JavaMail.zimbra@shaw.ca> References: , <1386855149.517584144.1524675530610.JavaMail.zimbra@shaw.ca> Message-ID: it doesn't stop automatically , what I was trying to convey is that once the Access front end starts "crapping out" the only immediate remedy is restarting the SQL instance. Jean-Paul Natola ________________________________ From: dba-SQLServer on behalf of Jim Lawrence Sent: Wednesday, April 25, 2018 12:58 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring Why does the SQL service stop? Jim ----- Original Message ----- From: "J- P" To: "Discussion concerning MS SQL Server" Sent: Tuesday, April 24, 2018 4:53:06 PM Subject: Re: [dba-SQLServer] sql performance monitoring Correct, Access functions- one thing i have always noted even when it was on the physical server is that the when ever you open any job , for example "Joe Blow reception " You open the job and lets say i want to print/preview proposal, or what equipment is going on the job- ALWAYS at the bottom of the screen in access it says "calculating..................." then it opens- 5,10 even 15 seconds on the average- when things get bad it can take 20-30 or more, or it will crash Access completely - That's when I get the infamous email or text "Access is acting up" or "We can't work" then I login , or tell them to login to the server and "restart the sql service" then everything returns to normal , at least by there standards And when i login the server (before restarting it ) sql maybe at 2gb cpu at like 5% The hyperv disk is Fixed VHDX Jean-Paul Natola ________________________________ From: dba-SQLServer on behalf of fhtapia at gmail.com Sent: Tuesday, April 24, 2018 5:24 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From jnatola at hotmail.com Wed Apr 25 12:38:01 2018 From: jnatola at hotmail.com (J- P) Date: Wed, 25 Apr 2018 17:38:01 +0000 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: <1386855149.517584144.1524675530610.JavaMail.zimbra@shaw.ca>, Message-ID: it ran just as crappy when it was physical as well- granted it was much older hardware- I just feel that the standard 5-to 15 seconds waiting on "calculating" or the 10-20 seconds waiting on "running query" on the front end suggests poor "coding" for lack of a better term and when running from RDS its even worse- After all were only talking about ~2gb DB and ~40mb Access f/e and AT MOST 20-30 concurrent users ________________________________ From: dba-SQLServer on behalf of Arthur Fuller Sent: Wednesday, April 25, 2018 1:11 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring One other thing concerning Access functions, including UDFs. Many Access functions have SQL equivalents, and most UDFs can be ported to SQL. Performance gains may not be dramatic regarding UDFs, however. Also, has it been considered that the big problem might be the VM? It might be useful to experiment with a dedicated server rather than a VM, on a weekend or sometime when nobody's using the system. Hardware is so inexpensive now that the performance penalty incurred by the VM software may not be worth it. A. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From jnatola at hotmail.com Wed Apr 25 13:21:35 2018 From: jnatola at hotmail.com (J- P) Date: Wed, 25 Apr 2018 18:21:35 +0000 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: <1386855149.517584144.1524675530610.JavaMail.zimbra@shaw.ca>, Message-ID: Irony, Just got the call Access is down Haaa? ________________________________ From: dba-SQLServer on behalf of Arthur Fuller Sent: Wednesday, April 25, 2018 1:11 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring One other thing concerning Access functions, including UDFs. Many Access functions have SQL equivalents, and most UDFs can be ported to SQL. Performance gains may not be dramatic regarding UDFs, however. Also, has it been considered that the big problem might be the VM? It might be useful to experiment with a dedicated server rather than a VM, on a weekend or sometime when nobody's using the system. Hardware is so inexpensive now that the performance penalty incurred by the VM software may not be worth it. A. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From accessd at shaw.ca Wed Apr 25 15:32:13 2018 From: accessd at shaw.ca (Jim Lawrence) Date: Wed, 25 Apr 2018 14:32:13 -0600 (MDT) Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: <1386855149.517584144.1524675530610.JavaMail.zimbra@shaw.ca> Message-ID: <950007487.518181837.1524688333177.JavaMail.zimbra@shaw.ca> Just a note, and this observation is at least a decade old; UDFs seemed to slow down performance and for that reason, at one point, I never used them. OTOH, newer version of MS SQL may have optimized these functions by loading them in memory. Oracle had that feature where an admin person could choose to keep certain functions loaded in memory or just make them sticky... Jim ----- Original Message ----- From: "Arthur Fuller" gmail.com> To: "Discussion concerning MS SQL Server" databaseadvisors.com> Sent: Wednesday, April 25, 2018 10:11:16 AM Subject: Re: [dba-SQLServer] sql performance monitoring One other thing concerning Access functions, including UDFs. Many Access functions have SQL equivalents, and most UDFs can be ported to SQL. Performance gains may not be dramatic regarding UDFs, however. Also, has it been considered that the big problem might be the VM? It might be useful to experiment with a dedicated server rather than a VM, on a weekend or sometime when nobody's using the system. Hardware is so inexpensive now that the performance penalty incurred by the VM software may not be worth it. A. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From accessd at shaw.ca Wed Apr 25 16:17:34 2018 From: accessd at shaw.ca (Jim Lawrence) Date: Wed, 25 Apr 2018 15:17:34 -0600 (MDT) Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: <1386855149.517584144.1524675530610.JavaMail.zimbra@shaw.ca> Message-ID: <615048258.518328093.1524691054862.JavaMail.zimbra@shaw.ca> My knowledge on the latest versions of MS SQL is limited. In the past the things I attended to was, never use pass-through queries (at times they can be excessively slow and unstable), only in rare occasions posted sql code directly from the Access FE to MS SQL (just passed variables and used SPs (stored procedures)...very much faster, more security and they never fail), always use ADO when connecting to the server (ADO has and is built into every Windows version from 2000 to Win10) instead of DAO (ADO is more stable, flexible and faster in a relatively fluid network environment...and you can mix and match; DAO local and ADO remote) and set up your SPs to monitor how many records are returned on any one request...if a million records are returned Access will surely crash...when using Access 2003-2007, it seems to top out at around 50K. One more item but this may not be a concern; how many connection licences do you have?...I used a system of locking the tables and used a count loop file to manage too many users trying to the access the MS SQL server...the locking looping was so quick no one ever noticed the small pause. The above described system that ran across all the regions, in the province and could have a hundred users pounding away at any one time. As far as I know, the system never failed. I have not been following this thread, so much of what I have added may have already been discussed at length. Jim ----- Original Message ----- From: "J- P" To: "Discussion concerning MS SQL Server" databaseadvisors.com> Sent: Wednesday, April 25, 2018 10:26:32 AM Subject: Re: [dba-SQLServer] sql performance monitoring it doesn't stop automatically , what I was trying to convey is that once the Access front end starts "crapping out" the only immediate remedy is restarting the SQL instance. Jean-Paul Natola ________________________________ From: dba-SQLServer databaseadvisors.com> on behalf of Jim Lawrence Sent: Wednesday, April 25, 2018 12:58 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring Why does the SQL service stop? Jim ----- Original Message ----- From: "J- P" To: "Discussion concerning MS SQL Server" databaseadvisors.com> Sent: Tuesday, April 24, 2018 4:53:06 PM Subject: Re: [dba-SQLServer] sql performance monitoring Correct, Access functions- one thing i have always noted even when it was on the physical server is that the when ever you open any job , for example "Joe Blow reception " You open the job and lets say i want to print/preview proposal, or what equipment is going on the job- ALWAYS at the bottom of the screen in access it says "calculating..................." then it opens- 5,10 even 15 seconds on the average- when things get bad it can take 20-30 or more, or it will crash Access completely - That's when I get the infamous email or text "Access is acting up" or "We can't work" then I login , or tell them to login to the server and "restart the sql service" then everything returns to normal , at least by there standards And when i login the server (before restarting it ) sql maybe at 2gb cpu at like 5% The hyperv disk is Fixed VHDX Jean-Paul Natola ________________________________ From: dba-SQLServer databaseadvisors.com> on behalf of fhtapia at gmail.com Sent: Tuesday, April 24, 2018 5:24 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From jnatola at hotmail.com Wed Apr 25 16:18:34 2018 From: jnatola at hotmail.com (J- P) Date: Wed, 25 Apr 2018 21:18:34 +0000 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: <950007487.518181837.1524688333177.JavaMail.zimbra@shaw.ca> References: <1386855149.517584144.1524675530610.JavaMail.zimbra@shaw.ca> , <950007487.518181837.1524688333177.JavaMail.zimbra@shaw.ca> Message-ID: so i tried IDERA sqldoc for 5 minutes (thanks Francisco) and you guys hit it on the head, it would appear to me (and please correct me if I'm wrong) that I now have evidence that it is not hardware/VM/server config causing poor performance. Missing index on [CLIENTDB_NAME].[dbo].[ScheduleItems] An implicit conversion on column [CLIENTDB_NAME].[dbo].[Inventory].[InvenConflict] to data type "tinyint" may be causing index suppression Duplicate index found on [CLIENTDB_NAME].[dbo].[JobHeader] Duplicate index found on [CLIENTDB_NAME].[dbo].[JobHeader] Single use Ad-hoc plans are using 92.1 MB of procedure cache ?? Index [SchedEmpID] on [CLIENTDB_NAME].[dbo].[ScheduleEmployees] is disabled The function "like" on column [CLIENTDB_NAME].[dbo].[Contacts].[Company] may be causing a table scan The function "like" on column [CLIENTDB_NAME].[dbo].[ScheduleItems].[JFunction] may be causing a table scan An implicit conversion on column [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data type "tinyint" may be causing index suppression An implicit conversion on column [CLIENTDB_NAME].[dbo].[Inventory].[InvenHideOnLoadSheet] to data type "tinyint" may be causing index suppression An implicit conversion on column [CLIENTDB_NAME].[dbo].[Inventory].[InvenDisplayItem] to data type "tinyint" may be causing index suppression An implicit conversion on column [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data type "tinyint" may be causing index suppression An implicit conversion on column [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Driver] to data type "tinyint" may be causing index suppression An implicit conversion on column [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data type "tinyint" may be causing index suppression An implicit conversion on column [CLIENTDB_NAME].[dbo].[Contacts].[Hide] to data type "tinyint" may be causing index suppression An implicit conversion on column [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data type "tinyint" may be causing index suppression An implicit conversion on column [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data type "tinyint" may be causing index suppression An implicit conversion on column [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data type "tinyint" may be causing index suppression An implicit conversion on column [CLIENTDB_NAME].[dbo].[Inventory].[InvenObsolete] to data type "tinyint" may be causing index suppression From: dba-SQLServer on behalf of Jim Lawrence Sent: Wednesday, April 25, 2018 4:32 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring ? Just a note, and this observation is at least a decade old; UDFs seemed to slow down performance and for that reason, at one point, I never used them. OTOH, newer version of MS SQL may have optimized these functions by loading them in memory. Oracle had that feature where an admin person could choose to keep certain functions loaded in memory or just make them sticky... Jim ----- Original Message ----- From: "Arthur Fuller" gmail.com> To: "Discussion concerning MS SQL Server" databaseadvisors.com> Sent: Wednesday, April 25, 2018 10:11:16 AM Subject: Re: [dba-SQLServer] sql performance monitoring One other thing concerning Access functions, including UDFs. Many Access functions have SQL equivalents, and most UDFs can be ported to SQL. Performance gains may not be dramatic regarding UDFs, however. Also, has it been considered that the big problem might be the VM? It might be useful to experiment with a dedicated server rather than a VM, on a weekend or sometime when nobody's using the system. Hardware is so inexpensive now that the performance penalty incurred by the VM software may not be worth it. From jnatola at hotmail.com Wed Apr 25 16:35:11 2018 From: jnatola at hotmail.com (J- P) Date: Wed, 25 Apr 2018 21:35:11 +0000 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: <615048258.518328093.1524691054862.JavaMail.zimbra@shaw.ca> References: <1386855149.517584144.1524675530610.JavaMail.zimbra@shaw.ca> , <615048258.518328093.1524691054862.JavaMail.zimbra@shaw.ca> Message-ID: its core licensing, not per user- good to know for other situations though thanks ________________________________ From: dba-SQLServer on behalf of Jim Lawrence Sent: Wednesday, April 25, 2018 5:17 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring My knowledge on the latest versions of MS SQL is limited. In the past the things I attended to was, never use pass-through queries (at times they can be excessively slow and unstable), only in rare occasions posted sql code directly from the Access FE to MS SQL (just passed variables and used SPs (stored procedures)...very much faster, more security and they never fail), always use ADO when connecting to the server (ADO has and is built into every Windows version from 2000 to Win10) instead of DAO (ADO is more stable, flexible and faster in a relatively fluid network environment...and you can mix and match; DAO local and ADO remote) and set up your SPs to monitor how many records are returned on any one request...if a million records are returned Access will surely crash...when using Access 2003-2007, it seems to top out at around 50K. One more item but this may not be a concern; how many connection licences do you have?...I used a system of locking the tables and used a count loop file to manage too many users trying to the access! the MS SQL server...the locking looping was so quick no one ever noticed the small pause. The above described system that ran across all the regions, in the province and could have a hundred users pounding away at any one time. As far as I know, the system never failed. I have not been following this thread, so much of what I have added may have already been discussed at length. Jim ----- Original Message ----- From: "J- P" To: "Discussion concerning MS SQL Server" databaseadvisors.com> Sent: Wednesday, April 25, 2018 10:26:32 AM Subject: Re: [dba-SQLServer] sql performance monitoring it doesn't stop automatically , what I was trying to convey is that once the Access front end starts "crapping out" the only immediate remedy is restarting the SQL instance. Jean-Paul Natola ________________________________ From: dba-SQLServer databaseadvisors.com> on behalf of Jim Lawrence Sent: Wednesday, April 25, 2018 12:58 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring Why does the SQL service stop? Jim ----- Original Message ----- From: "J- P" To: "Discussion concerning MS SQL Server" databaseadvisors.com> Sent: Tuesday, April 24, 2018 4:53:06 PM Subject: Re: [dba-SQLServer] sql performance monitoring Correct, Access functions- one thing i have always noted even when it was on the physical server is that the when ever you open any job , for example "Joe Blow reception " You open the job and lets say i want to print/preview proposal, or what equipment is going on the job- ALWAYS at the bottom of the screen in access it says "calculating..................." then it opens- 5,10 even 15 seconds on the average- when things get bad it can take 20-30 or more, or it will crash Access completely - That's when I get the infamous email or text "Access is acting up" or "We can't work" then I login , or tell them to login to the server and "restart the sql service" then everything returns to normal , at least by there standards And when i login the server (before restarting it ) sql maybe at 2gb cpu at like 5% The hyperv disk is Fixed VHDX Jean-Paul Natola ________________________________ From: dba-SQLServer databaseadvisors.com> on behalf of fhtapia at gmail.com Sent: Tuesday, April 24, 2018 5:24 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From stuart at lexacorp.com.pg Wed Apr 25 17:28:38 2018 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Thu, 26 Apr 2018 08:28:38 +1000 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: , <950007487.518181837.1524688333177.JavaMail.zimbra@shaw.ca>, Message-ID: <5AE10116.4046.3249A7F9@stuart.lexacorp.com.pg> Absolutely! Poor database and query designs causing multiple table scans (that incudes the "index supression" lines) will make queries very slow. On 25 Apr 2018 at 21:18, J- P wrote: > so i tried IDERA sqldoc for 5 minutes (thanks Francisco) and you > guys hit it on the head, it would appear to me (and please correct me > if I'm wrong) that I now have evidence that it is not > hardware/VM/server config causing poor performance. > > > Missing index on [CLIENTDB_NAME].[dbo].[ScheduleItems] > An implicit conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenConflict] to data type > "tinyint" may be causing index suppression Duplicate index > found on [CLIENTDB_NAME].[dbo].[JobHeader] Duplicate index > found on [CLIENTDB_NAME].[dbo].[JobHeader] Single use > Ad-hoc plans are using 92.1 MB of procedure cache > ?? Index [SchedEmpID] on > [CLIENTDB_NAME].[dbo].[ScheduleEmployees] is disabled > The function "like" on column > [CLIENTDB_NAME].[dbo].[Contacts].[Company] may be causing a > table scan The function "like" on column > [CLIENTDB_NAME].[dbo].[ScheduleItems].[JFunction] may be > causing a table scan An implicit conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenHideOnLoadSheet] to > data type "tinyint" may be causing index suppression An > implicit conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenDisplayItem] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Driver] to data type > "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column [CLIENTDB_NAME].[dbo].[Contacts].[Hide] to > data type "tinyint" may be causing index suppression An > implicit conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenObsolete] to data type > "tinyint" may be causing index suppression > > > > > > > > > From: dba-SQLServer on > behalf of Jim Lawrence Sent: Wednesday, April 25, > 2018 4:32 PM To: Discussion concerning MS SQL Server Subject: Re: > [dba-SQLServer] sql performance monitoring ? > > Just a note, and this observation is at least a decade old; UDFs > seemed to slow down performance and for that reason, at one point, I > never used them. OTOH, newer version of MS SQL may have optimized > these functions by loading them in memory. Oracle had that feature > where an admin person could choose to keep certain functions loaded in > memory or just make them sticky... > > Jim > > ----- Original Message ----- > From: "Arthur Fuller" gmail.com> > To: "Discussion concerning MS SQL Server" databaseadvisors.com> > Sent: Wednesday, April 25, 2018 10:11:16 AM > Subject: Re: [dba-SQLServer] sql performance monitoring > > One other thing concerning Access functions, including UDFs. Many > Access functions have SQL equivalents, and most UDFs can be ported to > SQL. Performance gains may not be dramatic regarding UDFs, however. > > Also, has it been considered that the big problem might be the VM? It > might be useful to experiment with a dedicated server rather than a > VM, on a weekend or sometime when nobody's using the system. Hardware > is so inexpensive now that the performance penalty incurred by the VM > software may not be worth it. > > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > From jnatola at hotmail.com Thu Apr 26 11:27:28 2018 From: jnatola at hotmail.com (J- P) Date: Thu, 26 Apr 2018 16:27:28 +0000 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: <5AE10116.4046.3249A7F9@stuart.lexacorp.com.pg> References: , <950007487.518181837.1524688333177.JavaMail.zimbra@shaw.ca>, , <5AE10116.4046.3249A7F9@stuart.lexacorp.com.pg> Message-ID: I don't know if this ok to post here, but would anyone be interested in, or recommend someone or company, to get this fixed? ________________________________ From: dba-SQLServer on behalf of Stuart McLachlan Sent: Wednesday, April 25, 2018 6:28 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring Absolutely! Poor database and query designs causing multiple table scans (that incudes the "index supression" lines) will make queries very slow. On 25 Apr 2018 at 21:18, J- P wrote: > so i tried IDERA sqldoc for 5 minutes (thanks Francisco) and you > guys hit it on the head, it would appear to me (and please correct me > if I'm wrong) that I now have evidence that it is not > hardware/VM/server config causing poor performance. > > > Missing index on [CLIENTDB_NAME].[dbo].[ScheduleItems] > An implicit conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenConflict] to data type > "tinyint" may be causing index suppression Duplicate index > found on [CLIENTDB_NAME].[dbo].[JobHeader] Duplicate index > found on [CLIENTDB_NAME].[dbo].[JobHeader] Single use > Ad-hoc plans are using 92.1 MB of procedure cache > Index [SchedEmpID] on > [CLIENTDB_NAME].[dbo].[ScheduleEmployees] is disabled > The function "like" on column > [CLIENTDB_NAME].[dbo].[Contacts].[Company] may be causing a > table scan The function "like" on column > [CLIENTDB_NAME].[dbo].[ScheduleItems].[JFunction] may be > causing a table scan An implicit conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenHideOnLoadSheet] to > data type "tinyint" may be causing index suppression An > implicit conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenDisplayItem] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Driver] to data type > "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column [CLIENTDB_NAME].[dbo].[Contacts].[Hide] to > data type "tinyint" may be causing index suppression An > implicit conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenObsolete] to data type > "tinyint" may be causing index suppression > > > > > > > > > From: dba-SQLServer on > behalf of Jim Lawrence Sent: Wednesday, April 25, > 2018 4:32 PM To: Discussion concerning MS SQL Server Subject: Re: > [dba-SQLServer] sql performance monitoring > > Just a note, and this observation is at least a decade old; UDFs > seemed to slow down performance and for that reason, at one point, I > never used them. OTOH, newer version of MS SQL may have optimized > these functions by loading them in memory. Oracle had that feature > where an admin person could choose to keep certain functions loaded in > memory or just make them sticky... > > Jim > > ----- Original Message ----- > From: "Arthur Fuller" gmail.com> > To: "Discussion concerning MS SQL Server" databaseadvisors.com> > Sent: Wednesday, April 25, 2018 10:11:16 AM > Subject: Re: [dba-SQLServer] sql performance monitoring > > One other thing concerning Access functions, including UDFs. Many > Access functions have SQL equivalents, and most UDFs can be ported to > SQL. Performance gains may not be dramatic regarding UDFs, however. > > Also, has it been considered that the big problem might be the VM? It > might be useful to experiment with a dedicated server rather than a > VM, on a weekend or sometime when nobody's using the system. Hardware > is so inexpensive now that the performance penalty incurred by the VM > software may not be worth it. > > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From scott.marcus at tsstech.com Thu Apr 26 12:47:44 2018 From: scott.marcus at tsstech.com (Scott Marcus) Date: Thu, 26 Apr 2018 13:47:44 -0400 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: , <950007487.518181837.1524688333177.JavaMail.zimbra@shaw.ca>, , <5AE10116.4046.3249A7F9@stuart.lexacorp.com.pg> Message-ID: I would be interested in fixing these issues for your company. Here is my phone number... 513-623-3965 Scott Marcus -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of J- P Sent: Thursday, April 26, 2018 12:27 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring I don't know if this ok to post here, but would anyone be interested in, or recommend someone or company, to get this fixed? ________________________________ From: dba-SQLServer on behalf of Stuart McLachlan Sent: Wednesday, April 25, 2018 6:28 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring Absolutely! Poor database and query designs causing multiple table scans (that incudes the "index supression" lines) will make queries very slow. On 25 Apr 2018 at 21:18, J- P wrote: > so i tried IDERA sqldoc for 5 minutes (thanks Francisco) and you > guys hit it on the head, it would appear to me (and please correct me > if I'm wrong) that I now have evidence that it is not > hardware/VM/server config causing poor performance. > > > Missing index on [CLIENTDB_NAME].[dbo].[ScheduleItems] > An implicit conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenConflict] to data type > "tinyint" may be causing index suppression Duplicate index > found on [CLIENTDB_NAME].[dbo].[JobHeader] Duplicate index > found on [CLIENTDB_NAME].[dbo].[JobHeader] Single use > Ad-hoc plans are using 92.1 MB of procedure cache > Index [SchedEmpID] on > [CLIENTDB_NAME].[dbo].[ScheduleEmployees] is disabled > The function "like" on column > [CLIENTDB_NAME].[dbo].[Contacts].[Company] may be causing a > table scan The function "like" on column > [CLIENTDB_NAME].[dbo].[ScheduleItems].[JFunction] may be > causing a table scan An implicit conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenHideOnLoadSheet] to > data type "tinyint" may be causing index suppression An > implicit conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenDisplayItem] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Driver] to data type > "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column [CLIENTDB_NAME].[dbo].[Contacts].[Hide] to > data type "tinyint" may be causing index suppression An > implicit conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenObsolete] to data type > "tinyint" may be causing index suppression > > > > > > > > > From: dba-SQLServer on > behalf of Jim Lawrence Sent: Wednesday, April 25, > 2018 4:32 PM To: Discussion concerning MS SQL Server Subject: Re: > [dba-SQLServer] sql performance monitoring > > Just a note, and this observation is at least a decade old; UDFs > seemed to slow down performance and for that reason, at one point, I > never used them. OTOH, newer version of MS SQL may have optimized > these functions by loading them in memory. Oracle had that feature > where an admin person could choose to keep certain functions loaded in > memory or just make them sticky... > > Jim > > ----- Original Message ----- > From: "Arthur Fuller" gmail.com> > To: "Discussion concerning MS SQL Server" databaseadvisors.com> > Sent: Wednesday, April 25, 2018 10:11:16 AM > Subject: Re: [dba-SQLServer] sql performance monitoring > > One other thing concerning Access functions, including UDFs. Many > Access functions have SQL equivalents, and most UDFs can be ported to > SQL. Performance gains may not be dramatic regarding UDFs, however. > > Also, has it been considered that the big problem might be the VM? It > might be useful to experiment with a dedicated server rather than a > VM, on a weekend or sometime when nobody's using the system. Hardware > is so inexpensive now that the performance penalty incurred by the VM > software may not be worth it. > > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com NOTICE: This electronic mail transmission is for the use of the named individual or entity to which it is directed and may contain information that is privileged or confidential. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of any information contained herein is prohibited. If you have received this electronic mail transmission in error, delete it from your system without copying or forwarding it, and notify the sender of the error by replying via email or calling TSS Technologies at (513) 772-7000, so that our address record can be corrected. Any information included in this email is provided on an ?as is? and ?where as? basis, and TSS Technologies makes no representations or warranties of any kind with respect to the completeness or accuracy of the information contained in this email. From stuart at lexacorp.com.pg Thu Apr 26 16:35:35 2018 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Fri, 27 Apr 2018 07:35:35 +1000 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: , <5AE10116.4046.3249A7F9@stuart.lexacorp.com.pg>, Message-ID: <5AE24627.3036.373F6FE4@stuart.lexacorp.com.pg> If remote working from Papua New Guinea is OK, I'd be interested :) Sounds like you need both a front end and back end re-design :( On 26 Apr 2018 at 16:27, J- P wrote: > I don't know if this ok to post here, but would anyone be interested > in, or recommend someone or company, to get this fixed? > > > > > > > ________________________________ > From: dba-SQLServer on > behalf of Stuart McLachlan Sent: Wednesday, > April 25, 2018 6:28 PM To: Discussion concerning MS SQL Server > Subject: Re: [dba-SQLServer] sql performance monitoring > > Absolutely! > Poor database and query designs causing multiple table scans (that > incudes the "index supression" lines) will make queries very slow. > > > On 25 Apr 2018 at 21:18, J- P wrote: > > > so i tried IDERA sqldoc for 5 minutes (thanks Francisco) and you > > guys hit it on the head, it would appear to me (and please correct > > me if I'm wrong) that I now have evidence that it is not > > hardware/VM/server config causing poor performance. > > > > > > Missing index on [CLIENTDB_NAME].[dbo].[ScheduleItems] An > > implicit conversion on column > > [CLIENTDB_NAME].[dbo].[Inventory].[InvenConflict] to data > > type > > "tinyint" may be causing index suppression Duplicate index > > found on [CLIENTDB_NAME].[dbo].[JobHeader] Duplicate index > > found on [CLIENTDB_NAME].[dbo].[JobHeader] Single use > > Ad-hoc plans are using 92.1 MB of procedure cache > > Index [SchedEmpID] on > > [CLIENTDB_NAME].[dbo].[ScheduleEmployees] is disabled > > The function "like" on column > > [CLIENTDB_NAME].[dbo].[Contacts].[Company] may be causing a > > table scan The function "like" on column > > [CLIENTDB_NAME].[dbo].[ScheduleItems].[JFunction] may be > > causing a table scan An implicit conversion on column > > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > > type "tinyint" may be causing index suppression An > > implicit conversion on column > > [CLIENTDB_NAME].[dbo].[Inventory].[InvenHideOnLoadSheet] to > > data type "tinyint" may be causing index suppression An > > implicit conversion on column > > [CLIENTDB_NAME].[dbo].[Inventory].[InvenDisplayItem] to data > > type "tinyint" may be causing index suppression An > > implicit conversion on column > > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > > type "tinyint" may be causing index suppression An > > implicit conversion on column > > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Driver] to data > > type > > "tinyint" may be causing index suppression An implicit > > conversion on column > > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > > type "tinyint" may be causing index suppression An > > implicit conversion on column > > [CLIENTDB_NAME].[dbo].[Contacts].[Hide] to data type > > "tinyint" may be causing index suppression An implicit > > conversion on column > > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > > type "tinyint" may be causing index suppression An > > implicit conversion on column > > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > > type "tinyint" may be causing index suppression An > > implicit conversion on column > > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > > type "tinyint" may be causing index suppression An > > implicit conversion on column > > [CLIENTDB_NAME].[dbo].[Inventory].[InvenObsolete] to data > > type > > "tinyint" may be causing index suppression > > > > > > > > > > > > > > > > > > From: dba-SQLServer on > > behalf of Jim Lawrence Sent: Wednesday, April 25, > > 2018 4:32 PM To: Discussion concerning MS SQL Server Subject: Re: > > [dba-SQLServer] sql performance monitoring > > > > Just a note, and this observation is at least a decade old; UDFs > > seemed to slow down performance and for that reason, at one point, I > > never used them. OTOH, newer version of MS SQL may have optimized > > these functions by loading them in memory. Oracle had that feature > > where an admin person could choose to keep certain functions loaded > > in memory or just make them sticky... > > > > Jim > > > > ----- Original Message ----- > > From: "Arthur Fuller" gmail.com> > > To: "Discussion concerning MS SQL Server" databaseadvisors.com> > > Sent: Wednesday, April 25, 2018 10:11:16 AM Subject: Re: > > [dba-SQLServer] sql performance monitoring > > > > One other thing concerning Access functions, including UDFs. Many > > Access functions have SQL equivalents, and most UDFs can be ported > > to SQL. Performance gains may not be dramatic regarding UDFs, > > however. > > > > Also, has it been considered that the big problem might be the VM? > > It might be useful to experiment with a dedicated server rather than > > a VM, on a weekend or sometime when nobody's using the system. > > Hardware is so inexpensive now that the performance penalty incurred > > by the VM software may not be worth it. > > > > > > > > _______________________________________________ > > dba-SQLServer mailing list > > dba-SQLServer at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > http://www.databaseadvisors.com > > > > > > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > From jnatola at hotmail.com Fri Apr 27 11:57:50 2018 From: jnatola at hotmail.com (J- P) Date: Fri, 27 Apr 2018 16:57:50 +0000 Subject: [dba-SQLServer] sql performance monitoring In-Reply-To: References: , <950007487.518181837.1524688333177.JavaMail.zimbra@shaw.ca>, , <5AE10116.4046.3249A7F9@stuart.lexacorp.com.pg>, Message-ID: it seems i don't always get messages, and sometimes i cant post- but anyone interested please email me off list jnatola at hotmail ________________________________ From: J- P Sent: Thursday, April 26, 2018 12:27 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring I don't know if this ok to post here, but would anyone be interested in, or recommend someone or company, to get this fixed? ________________________________ From: dba-SQLServer on behalf of Stuart McLachlan Sent: Wednesday, April 25, 2018 6:28 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] sql performance monitoring Absolutely! Poor database and query designs causing multiple table scans (that incudes the "index supression" lines) will make queries very slow. On 25 Apr 2018 at 21:18, J- P wrote: > so i tried IDERA sqldoc for 5 minutes (thanks Francisco) and you > guys hit it on the head, it would appear to me (and please correct me > if I'm wrong) that I now have evidence that it is not > hardware/VM/server config causing poor performance. > > > Missing index on [CLIENTDB_NAME].[dbo].[ScheduleItems] > An implicit conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenConflict] to data type > "tinyint" may be causing index suppression Duplicate index > found on [CLIENTDB_NAME].[dbo].[JobHeader] Duplicate index > found on [CLIENTDB_NAME].[dbo].[JobHeader] Single use > Ad-hoc plans are using 92.1 MB of procedure cache > Index [SchedEmpID] on > [CLIENTDB_NAME].[dbo].[ScheduleEmployees] is disabled > The function "like" on column > [CLIENTDB_NAME].[dbo].[Contacts].[Company] may be causing a > table scan The function "like" on column > [CLIENTDB_NAME].[dbo].[ScheduleItems].[JFunction] may be > causing a table scan An implicit conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenHideOnLoadSheet] to > data type "tinyint" may be causing index suppression An > implicit conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenDisplayItem] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Driver] to data type > "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column [CLIENTDB_NAME].[dbo].[Contacts].[Hide] to > data type "tinyint" may be causing index suppression An > implicit conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[ScheduleEmployees].[Inactive] to data > type "tinyint" may be causing index suppression An implicit > conversion on column > [CLIENTDB_NAME].[dbo].[Inventory].[InvenObsolete] to data type > "tinyint" may be causing index suppression > > > > > > > > > From: dba-SQLServer on > behalf of Jim Lawrence Sent: Wednesday, April 25, > 2018 4:32 PM To: Discussion concerning MS SQL Server Subject: Re: > [dba-SQLServer] sql performance monitoring > > Just a note, and this observation is at least a decade old; UDFs > seemed to slow down performance and for that reason, at one point, I > never used them. OTOH, newer version of MS SQL may have optimized > these functions by loading them in memory. Oracle had that feature > where an admin person could choose to keep certain functions loaded in > memory or just make them sticky... > > Jim > > ----- Original Message ----- > From: "Arthur Fuller" gmail.com> > To: "Discussion concerning MS SQL Server" databaseadvisors.com> > Sent: Wednesday, April 25, 2018 10:11:16 AM > Subject: Re: [dba-SQLServer] sql performance monitoring > > One other thing concerning Access functions, including UDFs. Many > Access functions have SQL equivalents, and most UDFs can be ported to > SQL. Performance gains may not be dramatic regarding UDFs, however. > > Also, has it been considered that the big problem might be the VM? It > might be useful to experiment with a dedicated server rather than a > VM, on a weekend or sometime when nobody's using the system. Hardware > is so inexpensive now that the performance penalty incurred by the VM > software may not be worth it. > > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com