I have been looking around and found similar questions but nothing specific to what I am having trouble with.
Problem:
I cannot get the SSIS proxy and SQL credentials configured correctly to impersonate a restricted-access service account for a SQL Agent job step that runs an SSIS package. The r...
When using of database specific features (instead of 3rd party solutions) is justified, especially on the beginning stage of the project?
Example: Postgres has full-text search, which do not support some features of search engines (i.e. facets) but is pretty acceptable for my needs. It requires...
I am wondering why people think migrating between different DB solutions is so common that you have to calculate with it even before having a single row of data
I just learned there are "graph databases" out there, which are more suited for two applications "search engine" and especially "gis".
To avoid discussions whether a relational DB is better suited and to make clear what kind of Database is needed, here some more details what I want to use it for...
> I just learned there are "graph databases" out there, which are more suited for two applications "search engine" and especially "gis".
> To avoid discussions whether a relational DB is better suited and to make clear what kind of Database is needed, here some more details what I want to use it for:
> 1. Application (Search Engine): Handling search engine data in a relational DB is slow because you'll have big tables with enormous indeces.
Have you ever tried to change the storage/database solution under a mildly complicated app? There are chances that you would throw away basically everything in this case, so I would not worry about binding to Postgres (or any other sane product). — dezso17 secs ago
@JzInqXc9Dg I don't use it, it's a toy. But some people like being able to step through their code line by line, and you can see the intermediates states of local variables. Comes down to personal preference in the end.
The children tables must have indexes in the columns that are pointed to the main table that you are trying to update.
For example: If you have a children table pointing to this table using a foreign key you must create indexes in this foreign keys or you will not able to update the main table.
On top of that it shows a ridiculous amount of ignorance towards the existing editions including the free developer edition which according to the OP is "out of his scope" and "costs astronomically" (at zero cost). — TomTom12 hours ago
That's not the worst example by far
ONE of the 3 free edition has a limit. Care to actually read more than one sentence? — TomTom2 hours ago
@MonsterMMORPG there has been some confusion. Express edition: 0 dollars, 1GB memory limit, 10GB per db, can be used in production. Developer edition: 0 dollars, no limits (same as Enterprise), not permitted in production. I guess when you meant free you meant the Express edition. In any case, if you do need a production edition and the Express doesn't cover you, yes, the cost is high. And please, all sides, refrain from calling names, this is a professional site. — ypercubeᵀᴹ2 mins ago
I just raised some non constructive flags for good measure
I am pretty sure this is not required by German law. For a counterexample, I am a DBA at a biggish German company, have superuser rights to all non-cloud based databases (there are quite some), and nobody ever required me shutting myself out. — dezso7 secs ago
My coworker wants to recycle old unuseful records in a table we expect to have a lot of churn on. (I.e use updates if possible instead of doing inserts all the time)
Oh man, some years ago I had to reverse engineer a ton of reports from a Practice Management Software called Nextgen
getting the SQL for the reports was a horror show because while we had a test instance up and running, there was lots of stuff actively being done. So I had to use profiler and couldn't figure out a good way to filter a lot of noise
but obtain the report sql I did, maybe 10-15 times.
all the next gen reports used mega-complicated SQL with lots of temp tables. I can't way to see if that @PaulWhite article provides any information that will make me think "they wrongly used temp tables in some cases" or not
is Value a keyword in TSQL? like, is it what you use to SELECT the returned value of a table valued func for instance?
I see a SELECT Value from <function>
and in the function itself i see a Value declared col in the return Table.
so maybe not. you just have to select the same cols built int he function's return table then i am guessing? i literally never use functions in SQL but i just discovered one i inherited
@JzInqXc9Dg it's unlikely that will cause you any trouble in the near future. SQL Server may implement the features that use that keyword after many versions. Or never. Still, it would be best to avoid it.
I think if I ever saw a partitioned #temp table, I'd probably fall over.
> Additionally table variables do not support INCLUDEd columns, filtered indexes (until 2016) or partitioning, #temp tables do (the partition scheme must be created in tempdb).
When using of database specific features (instead of 3rd party solutions) is justified, especially on the beginning stage of the project?
Example: Postgres has full-text search, which do not support some features of search engines (i.e. facets) but is pretty acceptable for my needs. It requires...
The children tables must have indexes in the columns that are pointed to the main table that you are trying to update.
For example: If you have a children table pointing to this table using a foreign key you must create indexes in this foreign keys or you will not able to update the main table.
