December 20, 2017 at 11:43 am
There were significant changes in 2016 to SQL columnstore indexes. I'm anxious to start using them in my data warehouse but I'm concerned about whether my super users who don't have a 2016 version of SSMS will be able to query them. Can someone give me some insight here?
December 20, 2017 at 12:36 pm
diana.bodell 56517 - Wednesday, December 20, 2017 11:43 AMThere were significant changes in 2016 to SQL columnstore indexes. I'm anxious to start using them in my data warehouse but I'm concerned about whether my super users who don't have a 2016 version of SSMS will be able to query them. Can someone give me some insight here?
First, I am concerned about users using SSMS as a normal tool for access databases.
Second, SSMS is now a separate download, and you and your users can download and install SSMS 17.4.
December 20, 2017 at 12:55 pm
Lynn, thank you for your response. We are not using Access databases, we are using SQL databases. My users are very qualified T-SQL coders in this case. The organization does not allow individual users to download anything and it takes a while to get them to do it for us, so I go back to my original question, which is whether I can use SSMS for SQL version 2014 to write queries against a table with a columnstore index.
Please advise.
December 20, 2017 at 1:00 pm
I didn't say you were using Access. You can download and use SQL Server Management Studio v17.4 and use it to access your SQL Server 2016 database servers and databases. I am currently using it to access SQL Server 2012, SQL Server 2014, SQL Server 2016, and hopefully soon SQL Server 2017.
December 20, 2017 at 1:01 pm
If your company doesn't allow it, get the powers that can to obtain it for your users.
SQL Server Management Studio is a separate download and not included with SQL Server anymore.
December 20, 2017 at 1:04 pm
But I can see why you thought that, my mind was working faster than my fingers, access should have been accessing in my first response.
December 20, 2017 at 1:06 pm
Thanks Lynn, clearly you are not willing or able to answer my question. I appreciate your suggestions.
You said "First, I am concerned about users using SSMS as a normal tool for access databases" . To me, this read as you are assuming we are using the tool for Access databases, not "to access databases". I did not ask you to judge what we are doing with our data. I just want a simple answer to a simple question. My environment is probably very different from yours in that our data warehouse is FOR people to self serve their data through queries and cubes and PowerBI. I make sure that anyone writing queries is trained on T-SQL. At any rate, whether or not we query the database with SSMS or not is not relevant to my question. I also told you we cannot download and install software on our own machines.
Hopefully someone will simply answer the question.
December 20, 2017 at 1:12 pm
diana.bodell 56517 - Wednesday, December 20, 2017 1:05 PMThanks Lynn, clearly you are not willing or able to answer my question. I appreciate your suggestions.You said "First, I am concerned about users using SSMS as a normal tool for access databases" . To me, this read as you are assuming we are using the tool for Access databases, not "to access databases". I did not ask you to judge what we are doing with our data. I just want a simple answer to a simple question. My environment is probably very different from yours in that our data warehouse is FOR people to self serve their data through queries and cubes and PowerBI. I make sure that anyone writing queries is trained on T-SQL. At any rate, whether or not we query the database with SSMS or not is not relevant to my question. I also told you we cannot download and install software on our own machines.
Hopefully someone will simply answer the question.
First, it was a simple statement of opinion, and if it offended you, then you took it the wrong way. My definition of power users does not include developers writing code.
Second, you are right, I don't know if SSMS 2014 will work with column store indexes in SQL Server 2016. I was suggesting that instead of worrying about that, that you (or your company) should consider downloading the latest version of SSMS since it is now separate from the SQL Server product. As I stated, it has no problems (at least in my use case) accessing SQL Server 2012 and newer SQL Server instances.
December 20, 2017 at 1:21 pm
Thank you Lynn. If I took it the wrong way, I apologize. It is often the case that people on forums like this immediately make judgments about the way things are being done before understanding the circumstances. I have a dba here who works for me who, when he got here, was appalled that we let ANYONE query our databases directly because he believed all data should be accessed through an application. That's not what BI or data warehousing is about and he now understands that. Our data warehouse is a service that my team provides to our organization and although we do limit access appropriately, we have super users who are not developers who "mine" the data or at least do some pretty advanced analytics using queries and PowerBI. I understand that many organizations do not have super users who are not developers who can query appropriately. Anyway, I hope you have a nice holiday!
December 20, 2017 at 2:01 pm
diana.bodell 56517 - Wednesday, December 20, 2017 11:43 AMThere were significant changes in 2016 to SQL columnstore indexes. I'm anxious to start using them in my data warehouse but I'm concerned about whether my super users who don't have a 2016 version of SSMS will be able to query them. Can someone give me some insight here?
the version of Management Studio does not have any effect on what commands you run in it, that is solely determined by the version on the server. I've regularly run commands against a SQL Server 2014 or 2016 instance from a 2008 Management Studio without problem even though I'm using features not in 2008. The only side effect is that intellisense obviously would not recognize any new commands, functions, or language constructs, but they will run on the server.
December 20, 2017 at 2:10 pm
diana.bodell 56517 - Wednesday, December 20, 2017 1:21 PMThank you Lynn. If I took it the wrong way, I apologize. It is often the case that people on forums like this immediately make judgments about the way things are being done before understanding the circumstances. I have a dba here who works for me who, when he got here, was appalled that we let ANYONE query our databases directly because he believed all data should be accessed through an application. That's not what BI or data warehousing is about and he now understands that. Our data warehouse is a service that my team provides to our organization and although we do limit access appropriately, we have super users who are not developers who "mine" the data or at least do some pretty advanced analytics using queries and PowerBI. I understand that many organizations do not have super users who are not developers who can query appropriately. Anyway, I hope you have a nice holiday!
Most of the engineers that find themselves writing T-SQL code are I would even consider proficient in SQL.
Still, moving to SQL Server Management Studio v17.4 should be on your radar. Also, look at R in SQL Server 2016 as well. Your BI developers may find it interesting as well.
December 20, 2017 at 2:27 pm
diana.bodell 56517 - Wednesday, December 20, 2017 11:43 AMThere were significant changes in 2016 to SQL columnstore indexes. I'm anxious to start using them in my data warehouse but I'm concerned about whether my super users who don't have a 2016 version of SSMS will be able to query them. Can someone give me some insight here?
From a query standpoint, it will work, even with a slightly older version of SQL Server. The query processing all occurs inside the server instance. The optimizer is what makes the choices whether or not the Columnstore index will be used by the query. For queries, and only queries, using, for example, a 2014 instance of SSMS, will work fine against 2016. There are other functions that may not work.
"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
December 20, 2017 at 2:28 pm
Chris Harshman - Wednesday, December 20, 2017 2:01 PMdiana.bodell 56517 - Wednesday, December 20, 2017 11:43 AMThere were significant changes in 2016 to SQL columnstore indexes. I'm anxious to start using them in my data warehouse but I'm concerned about whether my super users who don't have a 2016 version of SSMS will be able to query them. Can someone give me some insight here?the version of Management Studio does not have any effect on what commands you run in it, that is solely determined by the version on the server. I've regularly run commands against a SQL Server 2014 or 2016 instance from a 2008 Management Studio without problem even though I'm using features not in 2008. The only side effect is that intellisense obviously would not recognize any new commands, functions, or language constructs, but they will run on the server.
Nuts. I didn't notice this, despite the nice highlighting as an accepted answer. Sorry I typed exactly the same thing. Ah well, great minds etc.
"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
December 20, 2017 at 2:50 pm
Lynn Pettis - Wednesday, December 20, 2017 2:10 PMdiana.bodell 56517 - Wednesday, December 20, 2017 1:21 PMThank you Lynn. If I took it the wrong way, I apologize. It is often the case that people on forums like this immediately make judgments about the way things are being done before understanding the circumstances. I have a dba here who works for me who, when he got here, was appalled that we let ANYONE query our databases directly because he believed all data should be accessed through an application. That's not what BI or data warehousing is about and he now understands that. Our data warehouse is a service that my team provides to our organization and although we do limit access appropriately, we have super users who are not developers who "mine" the data or at least do some pretty advanced analytics using queries and PowerBI. I understand that many organizations do not have super users who are not developers who can query appropriately. Anyway, I hope you have a nice holiday!Most of the engineers that find themselves writing T-SQL code are I would even consider proficient in SQL.
Still, moving to SQL Server Management Studio v17.4 should be on your radar. Also, look at R in SQL Server 2016 as well. Your BI developers may find it interesting as well.
Damn, once again I thought faster than I typed.
Should have said: Most of the engineers that find themselves writing T-SQL code where I work I wouldn't even consider proficient in SQL.
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply