DataGrip display full geometry - postgis

How can I load the full geometry in JetBrains DataGrip ?
Why do I get 204 KB loaded when total is 1.75 MB. Due to this record not displayed on Geo Viewer.

It was implemented to prevent OOM issues.
Go to Preferences → Database → Data Views and set desired values for Max LOB length (bytes)

Related

Wrong SIZE, MAXSIZE and FILEGROWTH?

I know that basically while creating a database, the model system DB is copied so based on the pictures below:
Why the initial size is 3MB for PRIMARY file and 1MB for LOG If the documentation clearly says that It should be 8MB for versions above 2016 and 1MB for anything lower (I'm on this category as I'm using 2014)
I understand that a log file could grow to 2TB maximum but why the Model database says unlimited and the STACK database says limited to 2TB?
Assuming that the actual default size is indeed 3MB and 1MB, why on the disk, I see 2240 KB and 560 KB?
Although the documentation for 2016 and later versions do say that the initial size is 8MB, I can't find references to the 1MB initial size in the 2005, 2008, 2008 R2, 2012 and 2014 versions. I don't have a 2014 version at hand but in 2008 R2 the initial size of model is also 3MB, so it seems to be the default initial value (maybe you confused initial size with the default autogrow value of 1MB).
In this point the documentation doesn't seem to be 100% accurate, because in all versions prior to 2016 they list the default autogrow of the primary data file as 10% when the real value is 1MB. Also, for the model log file the maximum size is Unrestricted/Unlimited (if you do select * from model..sysfiles the value of the size column in log row is -1) but when you create a new database the maximum size of the log file is indeed 2TB, I think that this is explained by this paragraph of the 2014 documentation:
If you modify the model database, all databases created afterward will inherit those changes. For example, you could set permissions or database options, or add objects such as tables, functions, or stored procedures. File properties of the model database are an exception, and are ignored except the initial size of the data file.
So I think that the documentation just coalesce the two facts, meaning that the maximum value of the log file for new databases is 2TB.
Because that column of SSMS don't shows decimal values, so the real value has to be rounded to an integer. Instead of using ROUND() probably they use CEILING() just to be in safe side (at least for low values, if not a size of e.g. 490KB would be reported as 0MB).

MySql to SQL Server - SQL Server Migration Assistance tool is showing few tables

We have a database which has 511 tables and 'SQL Server Migration Assistance for MySQL' is showing only 31 tables. I am using Version-6.0.0. It is not showing any error in 'output' window.
Followed - https://www.youtube.com/watch?v=fXe4XL41jVE for migration.
I have a table which has 87120301 records, and this is the last table which is displayed. Is there any restrictions for this tool ?.
Is there any other tool I can use for this Big Data Migration?.
Total size of the database in MySQL is 37GB.
Made changes in Project Settings as follows.
General - Migration - Batch Size = 99999999 (Maximum value)
GUI - Maximum Row Number of Source = 999999999 (Maximum value)
Maximum Row Number of Target = 999999999 (Maximum value)
Its working now.

Copy from s3 to redshift

I am loading data to redshift from s3, using MANIFEST to specify load because I have to load 8k files (total dataset size ~1TB)
I am using SQLWorkbench to load this dataset, I am setting MAXERROR = 100000, but actual error occurring is greater than 100000 (MAXERROR=100000). I think SQLWorkbench had MAXERROR limit to 100000.
Is there any better way to do this ? any suggestion ?
If you actually have more than 100,000 errors in your data being imported I would suggest you need to go back to the source and correct the files. If that's not possible then you could try loading the data into a table with the problematic columns set to VARCHAR(MAX) and then you can convert them inside Redshift.

How to take screenshot of very large Database Diagram in SSMS?

I have created a diagram in SSMS for my database. There are approximately 120 tables are used in this diagram. the problem is that when I copy that diagram from the Edit->Copy Diagram to Clipboard and paste it to MSPaint it gives me error. Error getting the Clipboard data!. I have also tried Fast Stone Capture utility to capture scrolled window. But, it is not taking screenshot properly. So, How do I take screenshot of very large Database Diagram?
To minimize resizing in Microsoft word go to "page layout" and choose "size/more pagesizes" and set width and height to max(55,87 cm * 55,87 cm)

Max real space in a varbinary(max) in SQL Server

I am saving files (any type ) in a SQL table, using a varbinary(max), I find out that the max usage of this datatype is 8000, but what does the 8000 mean?
The online documentation says that is 8000 bytes. Does that mean that the maximum size of the file to be save there is 8000/1024 = 7.8125 KB?
I start testing and the maximum file that I can store is 29.9 MB. If I choose a larger file a get a SQLException.
String or binary data would be truncated. The statement has been
terminated.
Implement SQL Server 2012 (codename Denali) when it's released - it has FileTable feature :)
varbinary(8000) is limited by 8000 bytes - that's for sure!
varbinary(max) is limited by 2 gigabytes
varbinary(max) FILESTREAM is limited by your file system (FAT32 - 2 Gb, NTFS - 16 exabytes)
Taken from here:
http://msdn.microsoft.com/en-us/library/ms188362.aspx:
max indicates that the maximum storage size is 2³¹-1 bytes
which is 2 147 483 647 bytes. I'm not sure why it stops at 29.9MB.
What version of SQL Server are you using?
Varbinary on MSDN for SQL Server 2008 explicitly says that VarBinary(MAX) is for use when "the column data entries exceed 8,000 bytes."
Also, I would also take a look at the Filestream Capabilities in SQL Server 2008 if that is the server you are using.
I got the "String or binary data would be truncated" error when trying to store 5MB using varbinary(max) on SQL Server 2005. Increasing the autogrowth size for the database solved the problem. Took me a while to figure out, so just thought I'd share :)

Resources