Wednesday, September 02, 2009
Free SQL Server Training Videos
http://www.learnitfirst.com/Free/SQL-Server-Training.aspx
Labels: sql, sql server, sql server 2005, sql server 2008
Tuesday, June 30, 2009
Learn SQL Server with Online Training Videos
These aren't your run-of-the-mill training videos either. The videos from LearnItFirst.com are recorded by expert instructors and can be downloaded and watched anytime, anywhere. LearnItFirst.com also offers online training videos for Windows Server, Exchange Server and SharePoint Services, so check them out today!
Labels: sql dba, sql server
Tuesday, June 05, 2007
Why does Windows Update want to patch my already-patched SQL Server 2005?
Oh hell - just as I started trying to find the link to 3159, i noticed that a new hotfix is out dated two days ago: build 3161. It is really annoying at how they have been forced to throw out so many hotfixes post-SP2. Oh well - do you think they've learned their lesson so that we won't have this problem again? No? Me either... We went through this with Service Pack 2 for SQL Server 2000 as well you may remember if you've been around SQL Server for more than a few years.
Anyway, back on topic...
Here's a few helpful links to help you wade through the myriad of hotfixes and keep up-to-date:
- Aaron Bertrand has a comprehensive list going of all the hotfixes here
- SQL Server 2005 Service Pack 2 (SP2) Re-release and post fixes explained
Labels: sql, sql server, sql server 2005, sql server 2005 sp2
Monday, June 04, 2007
Download SQL Server 2008 Beta + SQL Server "Katmai" is Now Officially SQL Server 2008
If you want to download this first beta of SQL 2008, check it out here: https://connect.microsoft.com/SQLServer/content/content.aspx?ContentID=5395
It takes a good deal of logic problem solving to figure out this website but, once you do, you're in!
Labels: sql, sql server, sql server 2008
Monday, May 28, 2007
Weird Behavior With Stored Procedure Parameters That Are Delimited With Brackets
Basically, what we're seeing here is that, when you use brackets to delimit a parameterized expression in a stored procedure/function, your stored procedure will compile but it can never execute unless you override it's value. If, however, you try the same steps with a more declarative SQL, then it works fine.
It's quite odd and I just don't get it. I understand that brackets are a delimiter but why, as a stored procedure parameter, do they explicitly convert the argument to NVARCHAR? Has anyone see this before?
Labels: sql 2005, sql server
Saturday, May 26, 2007
New SQL Server Build (3161) + No October PDC!
PDC 2007 Canceled!
Yesterday, Microsoft canceled a developer conference - a big developer conference, the PDC. This is really, really odd in my opinion. If ever there was a year to have a developer conference, I would imagine this would've been it. Think about all the products released this year, last year and next year:
- Windows Vista
- Office 2007
- Exchange 2007
- SharePoint 2007/3.0
- Longhorn/Windows 2008
- Silverlight
- Ajax for ASP.NET
- Visual Studio Team Suite for Database Professionals (or whatever the hell that silly name is)
- SQL Server 2008 ("Katmai")
- Visual Studio 2008 ("Orcas")
We are currently in the process of rescheduling [emphasis mine] this fall’s Professional Developer Conference. As the PDC is the definitive developer event focused on the future of the Microsoft platform, we try to align it to be in front of major platform milestones. By this fall, however, upcoming platform technologies including Windows Server 2008, SQL Server codenamed "Katmai," Visual Studio codenamed "Orcas" and Silverlight will already be in developers' hands and approaching launch, which is where we’ll focus our developer engagement in the near term.I don't know what to think but I sure as hell don't believe the press release. I've read a few opinions from folks and one pundit said that he felt Microsoft just wasn't going to be ready for Windows 2008 by PDC and decided to bail. I don't know... I went to TechEd 2003 - paid the $1400 - with the express purpose of getting the prelaunch info on SQL Server 2003 lol. I was mad as #$#% when they announced a few days before the conference that SQL Server v.Next wasn't going to be released until 2004 (lol). As far as I was concerned, the whole conference was a wasted $1400. Therefore, if that is the reason, then I appreciate Microsoft canceling the conference.
I don't know - I'm rambling at this point... Anyway - just wanted to pass on the news about the new hotfix really.
Labels: sql server, sql server 2005
Thursday, April 05, 2007
SqlQueryStress - Handy Little SQL Performance Tool
It's too small to do a review on and besides, Adam made the software so easy to use that you really don't need much of a tutorial :) I did find a tiny bug when I was playing with it for the first time. If you type a query into the "Query" textbox, then click "Parameter Substitution", and then the "Get Columns" button, you get an error: "ExecuteReader: CommandText property has not been initialized." Obviously I shouldn't have clicked that button since my query had no parameters but it was my first time using it so I was just playing :)
I suggest you download it and play with it while it's free. It's very handy and who knows, Adam may get the bright idea to charge us for using his handy tool in the future! You can download it here. I particularly like the parameter substitution bit where I can take values from TableA and substitute them into queries against TableB. Adam posted a nice walk-through here.
Wishlist:
- I wish it would preserve my connection data between sessions
- I wish I could use GO to separate statements but an exception is raised
- I wish I had an option to dump the plan cache and buffer cache before running the "test"
- I tried adding DBCC FREEPROCCACHE, a GO, and then my query/proc but it failed. Once I removed the GO it was fine.
- I wish I could log the exceptions to a file
- I wish I could generate a report/something that would allow me to keep historical results of this information. The format is not important: .xml, .txt, .csv. I just want to be able to test a query, log the results, change something about the table/query/etc, run the query again, and compare results against previous execution.
Labels: sql 2005, sql server, sql server 2005
Friday, March 30, 2007
SQL Server 2005 Performance Dashboards Error: "the 'version_string' parameter is missing an attribute"
I successfully run SETUP.SQL so that it adds the necessary support objects into the MSDB but I cannot get a single report to run :(
I get a variety of errors:
- Report parameter 'session_id' was not found
- The 'version_string' parameter is missing a value
- Report parameter 'include_system_processes' is missing a value
I've tried this on two separate machines, one S.E. and one D.E. edition. Both are running 9.0.3050 (so don't ask if I have installed kb933508, cuz I have!).
Help! Anyone know why I'm getting these failures? I've googled/yahoo'ed and the only site I came up with was something in Russian and it didn't offer any solution (that I could tell).
Labels: sql 2005, sql server, sql server 2005
Tuesday, January 09, 2007
Happy New Year - Your Server Is Causing Errors Everywhere!
- Used the Control Panel/Services applet to change the SQL Server and SQL Agent service account passwords
- Nothing else
- FallBack certificate initialization failed with error code: 4
- The preLoginpacket used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.
- When trying to connect to my SSIS packages using SSMS: Client unable to establish connection
Encryption not supported on SQL Server. (MsDtsSrvr) [note: I can browse/open file-based packages just fine) - Failed to retrieve data for this request was also seen
- When trying to retrieve SSIS package info from a job: The LoadFromSqlServerMethod has encountered an OLE DB error code 0x80004005 (Client unable to establish connection...)
- When trying to run SSIS package from job: Executed as user: .\Administrator. The package could not be loaded. The step failed.
- All SSIS packages report an error upon opening:
- The description for Event ID '1073819649' in Source 'SQLISPackage' cannot be found
- SSIS An OLE DB error has occurred. Error code: 0x80040E4D (which was the result of it failing to remember my passwords when I typed them in after the previous error, I guess. Once I set the security to DoNoSaveSensitive and then saved it back to default of SaveWithUserKey it worked lol).
- There were errors while the package was being loaded.
The package might be corrupted.
See the Error List for details. - The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2005 Books Online.
- Of course I only have a single (default) instance of SQL 2005 on my machine
Anyway, I have resolved 80% of the errors above but I still cannot connect up to my SSIS packages stored in msdb nor can I execute any jobs :(
And you know what is perhaps the most annoying part about this? When I go to Google, type in any one of the error messages/codes above and then click on almost any of the Microsoft links returned, it tries to force me to LOG OUT or CREATE ACCOUNT - there is no Loginpage/link! It's either that or it returns results that require me to Loginon a different site to view the answer/post. Time for a new search engine?
I think this all stemmed from my not using the SQL Configuration Manager to change the passwords (instead, I used the Control Panel/Administrative Tools Services MMC snap-in). I know that I should use the Config Mgr but I didn't for whatever reason!
Labels: dts, integration services, sql, sql 2005, sql server, sql server 2005, ssis
