Tag Info

New answers tagged

0

You should insert the database name: sqlcmd -U ProvideLogin@Server -P ProvidePassword -S ProvideServerName -d ProvideDatabaseName https://msdn.microsoft.com/en-us/library/azure/ee336280.aspx


0

To resolve this error, try one of the following actions: Make sure that you have configured the firewall on the computer to allow this instance of SQL Server to accept connections. Use the SQL Server Configuration Manager tool to allow SQL Server to accept remote connections.


1

Without full-text search, no, there's no magic to making string parsing faster within SQL Server, other than pre-calculating results or throwing more resources at the problem. If you have a narrow set of search patterns that are repeated over and over again, it's possible you could maintain a skinnier materialized portion of the table that meet those ...


0

What you're describing sounds like parameter sniffing to me. Parameter sniffing occurs because SQL Server caches the execution plan of the procedure if the plan is not found in the cache. Subsequent executions will use that version of the plan. In most cases, that's desirable since it eliminates compilation time. However, if the characteristics of the data ...


0

Table compression is now supported in V12. You can compress the table to reduce the IO (as you mentioned CPU is not a problem). Try to batch the requests as each commit has overhead. You are just taling about 20 * 4 = 80 bytes per row and 80 * 4k = 320k data which is 0.5MB. This should be doable if tune the app in both S2 & S3. As you mentioned you are ...



Top 50 recent answers are included