One of the bloggers I follow is Brent Ozar. I tell you I’m a fan. I like the way he writes his stuff.
Anyway, he blogged about The Problem With SQL Server Training Today, and The Answer to SQL Server Training Problems a week or so ago. And this is the answer – SQLServerPedia – SQL Server Knowledge and Advice Straight from the Experts.
So in between giving out candies to cute little Indiana Joneses, pirates of the Caribbean, vampires and dead cheerleaders, I’ve been soaking in SQLServerPedia (geeky ‘no?). So far, so good. I’ll be a frequent flyer.
PS – and if you’re a DBA, you’ll find great laughs in this post : Somebody Created a Halloween Monster #SQLputdowns
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, ‘SQLVMSQL02’. (Replication.Utilities)
1. We configured database mirroring on 2 SQL Server instances.
2. We changed the computer name from SQLVM to SQL2K5.
3. We tried launching the Database Mirroring monitor, but we got the following error:
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, 'SQLVMSQL02'.
If you just look at the error, it sounds a bit misleading because we don’t have replication configured in either of the servers.
I previously posted about a SQL Server CheatSheet from DotNet4All that I thought was useful and comprehensive. If you already know what you need to do, but just forgot the syntax because you haven’t done it in eons, then a well organized, concise, complete cheat sheet can save the day.
Msg 5064, Level 16, State 1, Line 1
Changes to the state or options of database <your db name> cannot be made at this time. The database is in single-user mode, and a user is currently connected to it.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.”
1. Create your Visual Studio Project
2. Add the following references in your project
Here is a partial list of valid XSD data types for SQL Server 2005:
|xsd:int or xsd:integer
Brian Knight has posted a lot of good videos on JumpStartTV, including the following clustering videos:
Attribute-centric column ‘@Title’ must not come after a non-attribute-centric sibling in XML hierarchy in FOR XML PATH.