If it's a SAN then you might have the same problem that we had with Amazon

depends on your configuration

our connectivity was shared over a network connection which was also shared...

chris is correct

this is complex (mostly on the fact that we don't know your environment)

normally we see bloat in the log file (which is easy to fix)

but bloat in data...

easy - register all of your servers in management studio as a group (it will appear with a pink bar at the bottom of the screen)

click on the group and...

I'm not entirely convinced that i'm answering the right question since your English is a little broken (nothing wrong in that, it's my 3rd language)

if max mem is set to...

Sp_readrequest runs constantly, so it will show as a long running query - my vague understanding is that it uses the service broker to wait for a mail and then...

My go-to steps for those types of errors are to try ping-ing the server you are connecting to from the machine that cannot connect to make sure it can...

OK let me in on the alliteration joke

ok - this is only a guess

Via powershell, you might be using a different protocol (and hence a different port number) - the username and password has nothing to do...

if you can connect via powershell, but live cannot connect - 100% firewall, DNS or port issue

rvadim is correct

just take the single quotes out of the query. - however if you have stored this as varchar (which is madness) thenyou need to use convert or cast...

• This reply was modified 6 years, 5 months ago by MVDBA (Mike Vessey).

we're using Stretch - easy to configure and just silently puts your old records in the cloud, but allows you to query it like it was one table - there...

I don't think anyone can give you a good answer unless we have your table definition and a copy of the query that you think needs these indexes . even...

i'm not sure if this helps - but it does give you links for DB2 ODBC drivers

https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.apdv.cli.doc/doc/t0023867.html

I've seen this on the owner column when a user account has been removed - so have you upgraded recently (or restored from a different version) - maybe sp_helpdb doesn't...

there's one exception - your log file grows stupidly big...