Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
SQL Server 18.2 not using existing connection
Message
De
09/08/2019 14:46:29
 
 
À
09/08/2019 14:02:33
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Configuration
Divers
Thread ID:
01670007
Message ID:
01670012
Vues:
58
some stupid questions:
* is your network connection set to Public or Private? Typically you'd want it to be Private (assuming you're using an in-office network connection)
* Is this on a domain? or is using "peer-to-peer" mode with workgroup name?
* if using workgroup, when the username was created on the workstation, was it registered with an E-mail address? (a "feature" introduced in Windows 8 that could result in headaches if your network login username/password isn't identical to the one used for for E-mail -- which would likely be the case if the E-mail is on an offsite service).

>already been out there looking and what I'm finding is suggestions from other people, not necessarily MS, over the span of about 3-4 years.
>
>Doing some experimentation, it looks like it's tied to using Windows Authentication to connect to a Remote server. If I use SQL Server login, it's fine. If I log in using Window Authentication, I get the horrific lag, as do some of my co-workers.
>
>
>>Hi Dorris,
>>
>>I remember reading some time back a similar complain about another version in MSDN forum. Did you try to disable Intellisense (if there is an option)?
>>
>>Also, are you connecting to local DB or remote?
>>
>>My suggestion to you would be to try asking this question in MSDN SQL Server forums (probably Setup & Upgrade), there are lots of real experts hanging in these forums that would know the answer or you'll get attention from MS people.
>>
>>If you post there, can you please post here the link for the reference?
>>
>>Thanks.
>>
>>>They replaced our computers this month (YAY!)
>>>with Win10 machines (BOO)
>>>had to re-install all my software (BOO)
>>>didn't have to jury rig a connector for my 2nd monitor (YAY!)
>>>SQL Server 18.2 running like a scalded dog (YAY!)
>>>Machine decides it needs an update in the middle of the day (BOO)
>>>
>>>Now SQL Server takes forever (5-7 seconds or more) to do anything in the object explorer. (Yes, I've taken the time to time it, 'cuz I've GOT the time.)
>>>Expand DB - 6-9 seconds
>>>Expand tables/programmability - usually around 8 seconds
>>>Open new Query window - 10 seconds or more
>>>
>>>What I've tried:
>>>Repair Install - no love
>>>delete, restart, re-install - no love
>>>run as administrator - no love
>>>Googled possible fixes - no love
>>>
>>>I'm open to suggestions as this is so incredibly frustrating that I've been tempted to do many, MANY things that would end up with this machine returned to the lump of sand from which it came.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform