Microsoft SQL Server Administration resources and information - SearchSQLServer.com

SQL Server Administration

Email Alerts

Register now to receive SearchSQLServer.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • SQL Server stored procedures supercharged in recent, upcoming versions

    Microsoft is forever tinkering with SQL Server stored procedures to give queries more thrust. Find out what’s new in SQL Server 2008, 2008 R2 and the next-generation 2012 release.

  • Finding your way around SQL Server data preservation

    Need to know what a table looked like before changes were changes were made? There are several tools for SQL Server data preservation -- SQL Server change tracking and SQL Server database mirroring among them -- each with its own uses and limitations.

  • Top tips and tricks for SQL Server database development

    Check out these handy database development best practices, with tips on dealing with batch updates, stored procedures and more.

  • SQL Server errors, failures and other problems fixed from the trenches

    SQL Server expert Matthew Schroeder gets down into the trenches to help resolve your SQL Server issues. Whether it's a failed cluster installation, a long-running stored procedure that causes a 3 a.m. phone call or a database in suspect mode, he's got you covered with this handbook for DBAs on the SQL Server frontline.

  • Check SQL Server database and log file size with this stored procedure

    Knowing the size of a SQL Server database is one of the many DBA responsibilities that you can accomplish easily with the stored procedure sp_SDS. Not only will sp_SDS determine "SQL Database Space," but it can also be used to monitor database growth, alert a DBA on data or log file growth, execute a transaction log backup and even provide a detailed breakdown at the file level so a DBA can then shrink files with the most empty space.

  • SQL Server source code analysis and management adds database security

    Manage and protect your SQL Server databases by implementing source code analysis. Source code is the foundation of any application, and integrating methods to test and debug this code adds a key layer of security. IT security specialist Kevin Beaver explains why source code analysis should be a fundamental component of your SQL Server security measures.

  • Configure SQL Server Service Broker for sending stored procedure data

    The Service Broker feature in SQL Server 2005 allows you to queue data of stored procedures and other application development components. Instead of processing the data, it's sent to a queue where it can be automatically read at a later date and processed within the message. Follow these steps for setting up Service Broker and experience a rock solid communications' platform for transmitting data from one SQL Server system to another.

  • Find size of SQL Server tables and other objects with stored procedure

    When determining SQL Server disk space used by an object, Microsoft's sp_spaceused has limits. Here's an original stored procedure, sp_SOS, that calculates specific object space in SQL Server. Use it to get an overview of user table sizes in a database, the summary of the total space owned by a group of tables and to see the top 10 biggest indexed objects.

  • Use SQL Profiler to find long running stored procedures and commands

    Troubleshoot long running stored procedures with SQL Server Profiler by adding events to find the command with high run time.

  • Stored procedure to monitor long-running jobs in SQL Server 2000

    Monitoring long-running jobs in SQL Server 2000 is not a simple practice, but it is a best practice among DBAs. In this tip, try out a stored procedure that easily identifies long-running jobs. You'll also receive email alerts about these jobs that poorly affect SQL Server performance.

  • VIEW MORE ON : Stored Procedures
  • ODBC drivers replacing OLE DB? Say what?

    After years of telling SQL Server users to avoid ODBC in favor of OLE DB, Microsoft has suddenly reversed its position and advised going back to ODBC. Why? And what should you do about it?

  • Don’t sweat migration from Oracle, Sybase to SQL Azure

    Are you considering moving your database to Azure? Concerned about complexity? Read this tip from expert Denny Cherry. Migrating to SQL Azure might be the easiest move ever.

  • Cloaked in secrecy, Microsoft project aims to wed SQL, NoSQL databases

    Microsoft technical fellow David DeWitt is secretly developing a data management system that can do the jobs of both SQL and NoSQL databases. Can he bring the two sides together?

  • Five things in SQL Server not in SQL Azure

    With the excitement over the cloud, it’s easy to forget that Microsoft’s cloud database, SQL Azure, is not for everyone. Learn the five major differences between SQL Azure and SQL Server.

  • Microsoft gives tour of new release of SQL Server

    Microsoft gave PASS Summit 2010 attendees a walk-through of its Denali SQL Server release, demoing its AlwaysOn, FileTable and expanded SQL Server Integration Services features.

  • Utilize SSAS for data predictions and classification using Excel

    Using Excel as a tool for data mining and predictions is very powerful. Learn how to take advantage of SSAS in SQL Server 2005 with Microsoft Office Excel 2007.

  • How to create a SQL Server linked server to DB2

    Many SQL Server environments run DB2 servers, too, and often the two servers must be linked. Here's a step-by-step process that shows how to create a SQL Server linked server using Microsoft's DB2 driver.

  • Microsoft Access 2007 integration with SQL Server

    Microsoft Access 2007 introduces new features to boost integration with SQL Server.

  • SSIS package to filter false records

    I have a table, let's call it AlarmTriggers and it has a Boolean field pulled into it. When my software writes to it the table doesn't set the field to true. It's kept false. I want to use an SSIS package that filters all false records in the table and pull it over to another server. After the records have been pulled I would like the SSIS package to mark those pulled records as true. So, the source table field pulled must be set to true. I am using SQL Server 2005 Workgroup Edition. Can you tell me how to do this?

  • Efficiently push and pull data in SQL Server

    What is the most efficient way to 'PUSH' data from Sybase to MS SQL Server or 'PULL' data into MS SQL Server from Sybase?

  • VIEW MORE ON : Interoperability