Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
Does any one have idea about storing email boby in the sql server. The email body is about 15 lines. what has to be done inorder to maintain a table with 40 different emails contents.
Example:
a : some cotent should be sent
b : some other content
You'll probably want an nvarchar(max) column to store the contents of the body. This allows you to store up to 2GB worth of text...which is kind of a lot of text, so you should be good.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 days ago.
Improve this question
enter image description here
INSERT INTO #ApplicationFiles (OurBranchID, ApplicationFileNo)
SELECT
ApplicationDetails.x.value('OurBranchID[1]','nVarchar(12)'),
ApplicationDetails.x.value('ApplicationFileNo[1]','nVarchar(20)')
FROM
#ApplicationDetails.nodes('/JSON/dt_ApplicationDetails') AS ApplicationDetails(x)
The query is taking a long time to complete. I want to increase the performance of the query.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 days ago.
Improve this question
I have this requirement where I need to dump a large array of user Ids in one of the columns of a table in PostgreSQL DB. Let's say the max number of user Ids would be 100,000 and each user Id is of max 50 characters length. I won't be performing any operations on that table, it is just for logging purpose.
I've used text[] type column to dump those array of user Ids. I don't know if its the best way to do. I'm worried that some "max size limit reached" error gets thrown if the length of the array increases in the future.
Please suggest a better way to achieve this :)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
Sometimes I want to name a field in a table and this field is composed of a number of syllables!
I wonder how to select the most meaningful name in that case.
For example:
number of successions.
number of weekends
Should I write it:
NumberOfSuccessions
NumOfSuccessions
NumberSuccession
SuccessionNumbers
I care about my attribute naming because I'll deliver this to another developer and I want to get it smoothly.
You should select the first one, i.e. "NumberOfSuccessions" as that looks neat. It is always good to avoid short forms and keep the name as simple as plain english, wherever possible. Also avoid spaces as you have already done, just to make life simple.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I need to run kernel function 1 million times. In each core i need to create dynamic array of 1000 elements. How i can resolve this problem? Should i create buffer of 1 million * 1000 elements and contact them using id,but it's a lot of memory, and i haven't as much? Or is there another resolve?
Yes, you have to create a buffer of 1mil*1000, at least thats what i experienced.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
This question is out of pure curiosity.
Why do some systems and frameworks adopt a suffix on table and/or column names?
Example: the Activiti framework for business process uses the _ character at the end of every column name (ID_, VERSION_, NAME_, ...). I have notice that in some other systems as well.
I'm sure there is a good reason for that.
This is a convention for using names that can be saved words. When you want to call column "from" you can use "from_" because "from" is saved word of SQL.