@MaxVernon Seems like a decent database design question with six unopposed upvotes. I see @ypercubeᵀᴹ already voted to reopen, so I made a few extra formatting improvements and completed that process.
If you're using the command ALTER DATABASE [YourDatabaseName] QUERY_STORE CLEAR to "clean the query store" then behind the scenes it runs the following T-SQL statements:
TRUNCATE table sys.plan_persist_runtime_stats;
TRUNCATE table sys.plan_persist_runtime_stats_interval;
TRUNCATE table sys.plan...
I wanted to drop the foreighn key ,so i followed link & tried to find foreighn key constraint by below query :
SHOW CREATE TABLE ecomexpress_awb;
but it gave below result, its not showing foreighn key name , how to find foreighn key constraint , so that i can delete it....
@PaulWhite This is a really good read from a clearly very forward-thinking group of people. I am somewhat surprised by how few mods we have on dba.se - maybe something to do with the efficiency of said people :P
> It was inspired by what we learned by doing very little but watching great people take ownership of a new frontier while we tried to figure out where the magic was. Mostly in the hope that we didn’t break it.
@hot2use ...and how everyone maintains it. Everything contributes to the perceived quality of the site, from voting to comments to review queue tasks etc.
> Today, many of our 600+ moderators donate their time for over 10 hours a week – and some of them much longer – asking for nothing in return but the opportunity to know they’ve made it possible for learning communities like ours to continue to thrive.
...that's valid for a lot of community members here.
I think the culture here on the Heap has been a significant contributor to that. We've got a good group of regulars with a positive culture. It's very easy to slip into a mentality of dissing Lusers with contempt, but we've managed to avoid going that way here. The culture here has reflected in the attitudes of the regulars and moderators.
Probably January sometime. I'm going to be indisposed for December.
We used to have regular drinkies for the dba.se London regulars. I had a major operation and various other intrusions from real life that has interfered with it.
I'm not sure what the possibility of me venturing down south in the new year will be. Going live with the SAP replacement in January (hopefully). I'm expecting carnage
I have two tables namely table1 and table2, having size 9 GB and 200 MB size respectively.
Table 1 has 2 lac + records and Table 2 has 7 lac + records.
I'm using the below query for both BUT table 1 is taking forever to load records on higher offsets values WHILE table 2 is loading records so f...
A lakh or lac (/ˈlæk/ or /ˈlɑːk/; abbreviated L) is a unit in the Indian numbering system equal to one hundred thousand (100,000; scientific notation: 105). In the Indian convention of digit grouping, it is written as 1,00,000. For example, in India 150,000 rupees becomes 1.5 lakh rupees, written as ₹1,50,000 or INR 1,50,000.
It is widely used both in official and other contexts in Bangladesh, India, Myanmar, Nepal, Pakistan, and Sri Lanka. It is often used in Indian, Pakistani, and Sri Lankan English. In Pakistan, the word lakh is used mostly in local languages rather than in English media.
...
Scenario in short: A table with more than 16 million records [2GB in size]. The higher LIMIT offset with SELECT, the slower the query becomes, when using ORDER BY *primary_key*
So
SELECT * FROM large ORDER BY `id` LIMIT 0, 30
takes far less than
SELECT * FROM large ORDER BY `id` LI...
I'm in my home directory on my mac:
$ pwd
/Users/lukas
When I cd around, I do not (and can't) start the path with /:
$ cd Documents/
/Users/lukas/Documents
$ cd /Documents
-bash: cd: /Documents: No such file or directory
Except when I'm in /:
$ pwd
/
$ cd Users
/Users
$ cd /Users
/Users
...
I just had a quick question regarding table designs
I've got three relations that are basically identical, and I could merge them and just add a column to distinguish between things. But I'm unsure about doing this because of queries being slowed down if a 'master' table became too large
Apologies if this isn't the right place for a question!
With 20K rows per year, it can't become too large ;)
I have a similar case, with much more rows and we have 3-4 tables, all with similar structure. Having different tables helps with the procedures that write/update/delete from the tables.
The only issue is when we want a query that combines data from all of them
The decision to be made is whether to have 3 smaller, identical tables with a view that combines them all. Or whether to have one master table with 3 views
I'm still at university and this is my first DB project that will actually go into production so I'm just trying to make sure I get it right
@George.Palacios thanks, I'm basically the only guy working on this project for the company and they've pretty much left it in my hands so it's a bit daunting (fun though)
By 'right' I just don't want it to fall to pieces the moment I walk away and is decently speedy
do any of you PostgreSQL users think this question (10k+ only) is worth being undeleted? And, if so, can you provide a good answer? 2500+ views makes it seem like a fairly common problem.
@ypercubeᵀᴹ yah I saw that. It was originally closed as "too localized" which pretty accurately describes it. Just the view count makes me wonder if there is a place for it if it could have a good answer.