May 6, 2014 at 8:21 pm
Comments posted to this topic are about the item Removing Memory-optimized tables
May 7, 2014 at 12:19 am
Great question, had me do some research. First I thought the correct answer was listed as a "funny decoy". Turns out it wasn't... 😀
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
May 7, 2014 at 12:23 am
One more good question on new technology, did some research. Thanks!
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
May 7, 2014 at 12:40 am
+1. As I have also contributed the same question for QoTD and it is yet to published.However the nature of question is different 😉
--rhythmk
------------------------------------------------------------------
To post your question use below link
https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
🙂
May 7, 2014 at 4:56 am
Thank you for post, SJ. Interesting one.
Well, thanks to the local help files on SQL-2014, after reading the one of the limitations of memory-optimized file-groups (below), my mind generated list of questions, sequentially, so fast......, I am really not sure if these thought/s are valid or my mind is just babbling around, as I still very very new to this concept and it certainly going to need good amount of time to understand them.
QUOTE
Once you create a memory-optimized filegroup, you can only remove it by dropping the database. In a production environment, it is unlikely that you will need to remove the memory-optimized filegroup.
UNQUOTE
(that word... "unlikely" is bothering me a lot :-))
ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.
May 7, 2014 at 6:33 am
Nice question. I didn't know the answer, so had to look it up in BOL. I didn't use the reference provided in the explanation, because tehobvios place to look for this question seemed to be the BOL page called The Memory Optimized Filegroup because the page title looks right for this question. Using that page, like Raghu I came across that statement
In a production environment, it is unlikely that you will need to remove the memory-optimized filegroup
and started wondering (a) what I would do if that ever happened (that's easy if I can have sufficient down-time for a restore, but OLTP systems sometimes don't allow that) and (b) under what imaginable circumstances would I want to remove the filegroup (as opposed to moving the containers in it).
Tom
May 7, 2014 at 6:52 am
That was an excellent question. While I was surprised to find the answer while doing the research, it is what it is...until MS changes it. 😀 Thanks for a good one.
May 7, 2014 at 7:02 am
Raghavendra Mudugal (5/7/2014)
QUOTEOnce you create a memory-optimized filegroup, you can only remove it by dropping the database. In a production environment, it is unlikely that you will need to remove the memory-optimized filegroup.
UNQUOTE
😀 What about development and testing... I have then been unlikely ooops, unlucky having to remove the mo-fg about 20 times in my testing this week.:-D
May 7, 2014 at 7:05 am
Hmph. Since the question asked how to remove the filegroup from the database, I didn't consider dropping the database a viable option.
"Memory-optimized filegroups cannot be deleted."
http://msdn.microsoft.com/en-us/library/dn284308(v=sql.120).aspx
May 7, 2014 at 7:18 am
Eirikur Eiriksson (5/7/2014)
Raghavendra Mudugal (5/7/2014)
QUOTEOnce you create a memory-optimized filegroup, you can only remove it by dropping the database. In a production environment, it is unlikely that you will need to remove the memory-optimized filegroup.
UNQUOTE
😀 What about development and testing... I have then been unlikely ooops, unlucky having to remove the mo-fg about 20 times in my testing this week.:-D
Risk: 0
Experience: 1
🙂
ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.
May 7, 2014 at 7:32 am
Great question Steve. I had to do some research to figure it out, so I definitely learned something today.
May 7, 2014 at 7:42 am
Good question.
My problem is I am not certain that this implementation of the feature is very good. I can find where people would want to remove the in-memory filegroups. Needing to restore the database in order to remove the filegroups is a complete pita.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
May 7, 2014 at 1:34 pm
Thanks for the question Steve! I had to look this up too. Now knowing that the database would have to be dropped if I wanted to remove the filegroup, I would definitely want to test this out on a dev instance for a while before trying it in production!
May 7, 2014 at 3:44 pm
sestell1 (5/7/2014)
Hmph. Since the question asked how to remove the filegroup from the database, I didn't consider dropping the database a viable option."Memory-optimized filegroups cannot be deleted."
http://msdn.microsoft.com/en-us/library/dn284308(v=sql.120).aspx
+1
It's like asking how to remove a SQL Server instance from your server and you say that you can do it by reinstalling the OS. It works, but it's not exactly what you need.
May 7, 2014 at 4:27 pm
nice question..
thanks steve.
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply