HomeSQL ServerPage 569

SQL Server

Showing 11361 - 11380 of 14077 results
In this blog post, letโ€™s learn about the error message โ€œ256 โ€“ The data type %ls is invalid for the...
In this blog post, letโ€™s learn about the error message โ€œ33445 โ€“ The database โ€˜%.*sโ€™ is a readable secondary database...
In this blog post, letโ€™s learn about the error message โ€œ9432 โ€“ XML parsing: line %d, character %d, PUBLIC expectedโ€...
In this blog post, letโ€™s learn about the error message โ€œ41812 โ€“ ALTER TABLE on memory-optimized tables is not supported...
In this blog post, letโ€™s learn about the error message โ€œ16 โ€“ 13566โ€ in Microsoft SQL Server, the reason why...
In this blog post, letโ€™s learn about the error message โ€œ14883 โ€“ Stretch remote table creation failed without specific exception.โ€...
In this blog post, letโ€™s learn about the error message โ€œ40565 โ€“ Database copy failed. No more than 1 concurrent...
In this blog post, letโ€™s learn about the error message โ€œ15359 โ€“ Cannot add functional unit โ€˜%.*lsโ€™ to component โ€˜%.*lsโ€™....
In this blog post, letโ€™s learn about the error message โ€œ41127 โ€“ Attempt to set database mapping state where the...
In this blog post, letโ€™s learn about the error message โ€œ16 โ€“ 360โ€ in Microsoft SQL Server, the reason why...
In this blog post, letโ€™s learn about the error message โ€œ27142 โ€“ โ€˜%lsโ€™ is not a valid environment name. It...
In this blog post, letโ€™s learn about the error message โ€œ8119 โ€“ Column โ€˜%.*ls.%.*lsโ€™ is invalid in the HAVING clause...
In this blog post, letโ€™s learn about the error message โ€œ6255 โ€“ %s failed because type โ€œ%sโ€ does not conform...
In this blog post, letโ€™s learn about the error message โ€œ6226 โ€“ Type โ€œ%.*ls.%.*lsโ€ is marked for user-defined serialization, but...
In this blog post, letโ€™s learn about the error message โ€œ5503 โ€“ Unable to find entry in sys.database_files for FILESTREAM...
In this blog post, letโ€™s learn about the error message โ€œ14705 โ€“ Server Activityโ€ in Microsoft SQL Server, the reason...