digging a lot ... through SMMS, this query returns 44 table names that are present in the dbo schema
SELECT t.name
FROM sys.tables AS t
INNER JOIN sys.schemas AS s
ON t.[schema_id] = s.[schema_id]
WHERE s.name = N'dbo';
this is true regardless of what database I hit (prod 1, prod2, dev 1, etc)
when I run that from rails c, i get
irb(main):006:0> results = Location.connection.exec_query("SELECT t.name FROM sys.tables AS t INNER JOIN sys.schemas AS s ON t.[schema_id] = s.[schema_id] WHERE s.name = N'dbo'")
SQL (25.5ms) SELECT t.name FROM sys.tables AS t INNER JOIN sys.schemas AS s ON t.[schema_id] = s.[schema_id] WHERE s.name = N'dbo'
=> #<ActiveRecord::Result:0x007fe390734800 @columns=["name"], @rows=[["spt_fallback_db"], ["spt_fallback_dev"], ["spt_fallback_usg"], ["spt_monitor"]], @hash_rows=nil, @column_types={}>
when pointing to the prod database where the query is failing. When I run it on the prod database where the Location query works, it sees all 44 tables as expected.
So, ultimately, i agree ... it is a perms issue.
remote:
remote: current directory: /tmp/bundle/gems/tiny_tds-2.1.1/ext/tiny_tds
remote: /usr/local/.rbenv/versions/2.3.3/bin/ruby -r ./siteconf20180314-3087-2d24bj.rb
remote: extconf.rb
remote: checking for sybfront.h... yes
remote: checking for sybdb.h... yes
remote: checking for tdsdbopen() in -lsybdb... yes
remote: checking for dbanydatecrack() in -lsybdb... no
remote: Failed! Do you have FreeTDS 0.95.80 or higher installed?
remote: extconf.rb failed
remote: Could not create Makefile due to some reason, probably lack of necessary
remote: libraries and/or headers. Check the mkmf.log file for more details. You may
remote: need configuration options.
remote:
remote: Provided configuration options:
remote: --with-opt-dir
remote: --without-opt-dir
remote: --with-opt-include
remote: --without-opt-include=${opt-dir}/include
remote: --with-opt-lib
remote: --without-opt-lib=${opt-dir}/lib
remote: --with-make-prog
remote: --without-make-prog
remote: --srcdir=.
remote: --curdir
remote: --ruby=/usr/local/.rbenv/versions/2.3.3/bin/$(RUBY_BASE_NAME)
remote: --help
remote: --with-freetds-dir
remote: --without-freetds-dir
remote: --with-freetds-include
remote: --without-freetds-include=${freetds-dir}/include
remote: --with-freetds-lib
remote: --without-freetds-lib=${freetds-dir}/lib
remote: --with-freetds-dir
remote: --without-freetds-dir
remote: --with-freetds-include
remote: --without-freetds-include=${freetds-dir}/include
remote: --with-freetds-lib
remote: --without-freetds-lib=${freetds-dir}/lib
remote: --with-sybdblib
remote: --without-sybdblib
remote: --with-sybdblib
remote: --without-sybdblib
remote:
remote: To see why this extension failed to compile, please check the mkmf.log which can
remote: be found here:
remote:
remote: /tmp/bundle/extensions/x86_64-linux/2.3.0-static/tiny_tds-2.1.1/mkmf.log
remote:
remote: extconf failed, exit code 1
remote:
remote: Gem files will remain installed in /tmp/bundle/gems/tiny_tds-2.1.1 for
remote: inspection.
remote: Results logged to
remote: /tmp/bundle/extensions/x86_64-linux/2.3.0-static/tiny_tds-2.1.1/gem_make.out
remote:
remote: An error occurred while installing tiny_tds (2.1.1), and Bundler cannot
remote: continue.
remote: Make sure that
gem install tiny_tds -v '2.1.1' succeeds before bundling.remote: An error has occurred during web site deployment.
remote: bundler failed
hello guys, i have a question about the limit method as i am having an issue with pagination.
the code records.page(1).limit(10)
gives this sql command: ... [users].[id] IN (1, 2, 3, 4, 9, 3, 5, 8, 10, 6)
notice that the ID = 3 is used twice.. resulting in incorrect pagination (returning 9 records instead of 10), any help is appreciated on how to fix this.
@KDGundermann I think the reason is the "includes" vs "left_joins".Device.left_joins(:health_records).order('health_records.error_number desc').page(1).limit(10).count returns 10
Device.includes(:health_records).order('health_records.error_number desc').page(1).limit(10).count returns 3
MyRecord.where(field_name: value).take now fails with ActiveRecord::StatementInvalid:TinyTds::Error: Invalid column name '"TicketNo", "UniqueID", "ItemNo"'.: EXEC sp_executesql N'SELECT [Tkscale].* FROM [Tkscale] WHERE [Tkscale].[TicketNo] = @0 ORDER BY [Tkscale].["TicketNo", "UniqueID", "ItemNo"] ASC OFFSET 0 ROWS FETCH NEXT @1 ROWS ONLY', N'@0 nvarchar(max), @1 int', @0 = N'10234770', @1 = 1 which is odd since I didn't ask for the ordering. I'm not sure how to fix this. I have set MyRecord.table_name = 'Tkbatch' and MyRecord.primary_key = :UniqueId. MyRecord.connection.schema_cache.primary_keys("Tkbatch") returns ["TicketNo", "UniqueID", "ItemNo"]. I can't find an issue or in the code where this should be addressed. any ideas?
order but that's kind of a workaround
"Unable Adaptive Server connection failed (servername.database.secure.windows.net:1433)"
tiny_tds (2.1.2) lib/tiny_tds/client.rb:60:in 'connect'
tiny_tds (2.1.2) lib/tiny_tds/client.rb:60:in 'initialize'
If I look at the username of the opts being passed to
connect is has the wrong username. There was an @server automatically appended to it. I don't know if that is what the problem might be?
connect server name not founderror. I'm thinking this is just for connecting to a local sql server, and not one that is on a completely different machine. Can anyone point me in the right direction?
Perhaps I'm missing something, is there a way to define an Identity column that is not a primary key?
I am working with a legacy database which has some non-PK identity columns. When a performed a schema dump against our development database nothing seems to indicate that these columns are to be auto incremented.
