SQL Server

Today I received the following error while trying to check in some code after a marathon night of coding: TF30042: The database is full. Contact your Team Foundation Server administrator. I got one of those “oh crap” sinking feelings, that some how my TFS server had decided to just die. After doing a little research on this error, which there is very little (read close to none) information about on the internet. So I gave up searching and decided to do a little trial and error adhock testing, and I found out that this error has nothing to do with the database but everything to do with the size of the database’s log file. I came up with the following solution, that you will want to run in Microsoft SQL Server Management Studio: ...

I just recently read Jeff Atwood’s Deadlocked! article. I just wanted to give some more insight in to the read committed snapshot so that it is not perceived as “magic”. It has some definite advantages when dealing with deadlocks, however if your code relies on row level locking you are not going to be able to use this type of reading in SQL Server. First lets talk about how you enable it. It is not a transactional isolation level, so if you set it, it will effect your whole database. You have been warned! ...

I have been a huge fan of MySQL for a long time. It is the perfect database for when the budget is tight or you are not working in a Microsoft Environment. It performs well, and has a huge following of dedicated professional programmers that use it day in and day out on some of the largest websites on the planet. Most noteable Facebook, Twitter, Flickr, and Digg. Even with all these proven capabilities to scale and perform, Microsoft has choosen to ignore it and focus on some of the monolytic providers of databases such as IBM and Oracle when comparing SQL Server. ...

Recently I change the network name of one of my servers at work, because the box changed its job from a virtual machine server to the database server. Everything was going great until I decided to setup the server for replication and received the following error message. New Publication Wizard SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, ‘old_name’. (Replication.Utilities) OK So with a little hunting and SQL queries I found out that SQL Server doesn’t use the network name, it only excepts that as an alias. My SQL Server instance was still named “old_name”. I found that out by running these two queries: ...

I haven’t even herd of a new version of SQL Server 2008, coming out, but according to this blog the new version has some very interesting and new data types that will come in useful for geography processing. DATE - ANSI-compliant date data type TIME - ANSI-compliant time data type with variable precision DATETIMEOFFSET - timezone aware/preserved datetime DATETIME2 - like DATETIME, but with variable precision and large date range ...

Many developers use a pattern called ORM or Object Relation Mapping to generate data layers for their application. Many other developers choose to create their own data layers by hand. I have done both and I don’t have a preference of one over the other. With an ORM generator you have an easy to maintain data layer for your applications, when you create one by hand you have much more control of the data layer as far as object creation goes. ...

As you may all know I have Windows Vista Ultimate x64 and last post I talked about upgrading to SQL Server 2005 SP2. However while starting my first Database Project I encountered the following error. Microsoft Visual Studio An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) OK It has basically taken me around 24 hours to finally find a solution. The solution was so simple, but yet totally undocumented on if you encounter this error do this. So I am hoping to at least correct that with this post for all the future Googler’s out there. ...

Microsoft with out much fan far released service pack 2 for SQL Server 2005. There is a whole laundry list of new features and bug fixes listed on MSDN. However one of the biggest features at least for early adopters is the support for Windows Vista both x86 and x64 versions of the operating system. This release brings with it a great new tools for Windows Vista that are not available for previous operating systems. ...