New answers tagged

0

You are querying the wrong table - that item is probably set to be "Numeric (unsigned)", and you should query the history_uint table instead.


-1

This will help you to solve you SQL Connection Issues. https://blogs.msdn.microsoft.com/docast/2014/10/24/tips-and-tricks-to-fix-sql-connectivity-issues/


0

I believe you mean arrays? insert into fieldname values ('{"(1,2)","(2,3)"}') Naturally, this is documented.


0

Just delete (rename) registry key: HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server via (http://blog.dotsmart.net/2012/01/04/solution-for-package-microsoft-sql-management-studio-package-failed-to-load)


1

Any directory in MySQL datadir is considered as database by MySQL. Most likely you have dedicated mount point for /var/lib/mysql with ext{4,3,2} filesystem and default 'lost+found' directory present (lost+found directory is used by file system check tools (fsck)). You can say MySQL to treat this directory as directory and not database with the help of ...


1

Probably this might help others. adduser mysql chown mysql:mysql -R /var/lib/mysql sudo chmod -R 755 /var/lib/mysql/ sudo service mysql start


0

This will fix your problem bunzip2 -dk dump.sql.bz2 # or bunzip2 -ck dump.sql.bz2 > myfile.sql -c switch are mean to output to stdout, you must point the stdout result to somewhere when you use -c


0

Well, I found why. My SQL dump was compressed two times, but name was not dump.sql.bz2.bz2, just dump.sql.bz2. Binary file was the decompression result of only first layer. Mac OS Archive Utility is more intelligent because it recognized this double compression and had restored the original SQL dump file.


0

You certainly can, but not via transport rules. Hence these only allow basic HTML and these {{name}} attributes. You might want to look at this. It describes how to create custom transport agents. These would allow you to modify any outgoing message with the full ability of .NET and C#.


0

SQL Server is telling you it can't find some of your system databases (model and MSDB). Verify that the files exist and that SQL Server has permission to access them. SQL is looking in E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj, and that's where they should be. If they're not there, restore them from backup. (Did someone delete ...



Top 50 recent answers are included