I am 99% certain the user is hard core gaming the system and something is way way up.
There is no way you can be that stupid and have that much rep.
Everyone of his questions is crap
Most of them are some seemingly automatic generation of official docs that replace specific identifiers with metasyntatic variables. Which, if true, is awesome.
If he really exists. He's a "Question Squatter" and that's always awesome. That totally undermines so much of the incentive system..
@EvanCarroll in that (deleted) answer was not clear that the code was meant to work in SQL Server (and version v.Next). That's one of the reasons you got downvotes (and the "upgrade to Postgres" did not help either ;) The link from JamesAnderson above has the syntax.
@TomV no kidding. They probably like being strangled while having sex, too.
Is the server running on a mobile phone from 2002? All kidding aside, there are a lot of possible reasons. Have you checked anything? — Max Vernon28 secs ago
Q: I need to pass Millions of parameters in WHERE IN clause, below is the scenario mentioned:
I've two database servers SourceDB-server & DestinationDB-server,
I need to Sync data from SourceDB TO DestinationDB, so I'm generating query dynamically through C# code, final query is mentioned below...
I installed SQL Server on RHEL7 VM
msodbcsql-13.1.1.0-1.x86_64
mssql-server-14.0.100.187-1.x86_64
mssql-tools-14.0.2.0-1.x86_64
# ls -al /opt/
total 4
drwxr-xr-x. 5 root root 52 Jan 13 08:31 .
drwxr-xr-x. 17 root root 4096 Jan 13 07:55 ..
drwxr-xr-x. 3 root root 22 Jan 13 08:31 microsoft
...
@hot2use I considered it, but I'm not sure how useful that is. Consider next as an example. What is "next"? I understand vNext is how Microsoft is referring to their upcoming version, but once it is released, what will vnext refer to?
Microsoft is referring to their upcoming version of SQL Server as "vNext".
Should we add vnext?
I think the transient nature of the word "next" indicates this would be a bad candidate tag since questions tagged with it will eventually not actually refer to the new "vNext".
@MaxVernon True. But people might start looking for vNext information and until the version is out, what better way to channel the google searches? You could then have a synonym refer to [sql-server-2017nix] or whatever MS comes up with.
@swasheck that's what i initially thought too, but it explicitly tells you to copy the tempdb files from the old location to the new, when moving tempdb. Which you don't need to do on Windows.
Microsoft is referring to their upcoming version of SQL Server as "vNext".
Should we add vnext?
I think the transient nature of the word "next" indicates this would be a bad candidate tag since questions tagged with it will eventually not actually refer to the new "vNext".
@ypercube i've already got a solution using CASE, but i was wondering if you knew of any other way to work around the possibility of dividing by ln(1)?
@jcolebrand would you represent that as NULL? we have legacy databases with autogrow as a percentage and i've been tasked with forecasting when they'd hit maxfilesize
@jcolebrand there are several types of Infinity. Usually we don't need arithmetic with them. Even those that we do (define and do arithmetic with), 1^SomeInfinity = 1
Isnt' GrowthRate either a MB size or a percentage?
You shouldn't ever be doubling in size, so it should be something like 1.1 (for 10% growth)
Wait, I'm skipping a step
If it's 10% growth rate this becomes a recursive iteration
If it's megabytes then the equation above is correct, and you should fatally fail on values that are 1 so you can go do maintenance and fix them to be something valid
@jcolebrand i figured it out. i told you that GrowthRate is actual = 1+AutoGrowthRate and then didnt actually edit the equation ... edited and now it's correct. i think that's what i have originally, but didnt reverse-engineer the equation correctly here
Here is one.. If I'm right in my answer -- I may not be. I think that VERBOSE is super crap for postgresql in this case. dba.stackexchange.com/a/161042/2639
Let us never say that I was mute on PostgreSQL's warts.
Q: I need to pass Millions of parameters in WHERE IN clause, below is the scenario mentioned:
I've two database servers SourceDB-server & DestinationDB-server,
I need to Sync data from SourceDB TO DestinationDB, so I'm generating query dynamically through C# code, final query is mentioned below...
I installed SQL Server on RHEL7 VM
msodbcsql-13.1.1.0-1.x86_64
mssql-server-14.0.100.187-1.x86_64
mssql-tools-14.0.2.0-1.x86_64
# ls -al /opt/
total 4
drwxr-xr-x. 5 root root 52 Jan 13 08:31 .
drwxr-xr-x. 17 root root 4096 Jan 13 07:55 ..
drwxr-xr-x. 3 root root 22 Jan 13 08:31 microsoft
...
Microsoft is referring to their upcoming version of SQL Server as "vNext".
Should we add vnext?
I think the transient nature of the word "next" indicates this would be a bad candidate tag since questions tagged with it will eventually not actually refer to the new "vNext".
