Skip to main content

How to test a connection string on the server

By
De cate ori nu ati patiti sa ajungeti pe un server unde ati facut deploy la o aplicatie si sa va treziti ca nu aveti conexiune la baza de date?
O soluție simpla pentru a testa conectivitatea la o baza de date SQL Server, fără sa fie nevoie sa instalați sau copiați o aplicație este sa ne folosim de un fișier uld (Universal Data Link).
  1. Creați un fișier cu extensia udl (fisier nou in nodepad si "save as" cu extensia udl)
  2. Dublu click pe el, iar apoi mergeți la tab-ul "properties"
  3. Selectați providerul (in cazul nostru SQL Express)
  4. Adaugați datele de conexiune (ip, user parola)
  5. Apăsați butonul de "Test Connection"
Daca testul de conexiune se termina fără succes înseamna ca baza de date nu este accesibila.
Labels:

Comments

  1. TudorOctober 21, 2011 at 5:26 PM

    Din cate tin minte, UDL-urile merg doar cu provideri OleDB, care in viitoarele versiuni de SQL Server nu prea va mai fi suportat..

    ReplyDelete
  2. Radu VunvuleaOctober 21, 2011 at 7:21 PM

    Dar pana atunci si mult timp dupa o sa mai gasim servere cu aceasta configuratie.

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more