Skip to main content

How to test a connection string on the server

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.


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

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


Post a Comment

Popular posts from this blog

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

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 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.51EF 6.0.2VS2013
It seems that there …

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…