This month's discount Comprehensive Database Performance Health Check · Testimonials
SQLAuthority with Pinal Dave
Home
  • Consulting
    • Health Check
  • Free Videos
  • All Articles
    • AI
    • SQL Performance
    • SQL Tips and Tricks
    • Interview Questions and Answers
    • SQL Puzzle
    • SQL Video
    • SQLAuthority News
    • Personal
  • Books
  • Consulting
SQL SERVER - Fix: Error Msg 128 The name is not permitted in this context. Only constants, expressions, or variables allowed here. Column names are not permitted.

SQL SERVER – Fix: Error Msg 128 The name is not permitted in this context. Only constants, expressions, or variables allowed here. Column names are not permitted.

March 22, 2007
Pinal Dave
SQL Performance
SQL Download, SQL Error Messages, SQL Scripts, SQL Server Security

Msg 128, The name is not permitted in this context, shows up when one column is used as the DEFAULT of another. Use only constants, expressions or variables.

Read More
A stick insect hidden among twigs in a hedge, given away only by its thin red legs

Auditing Who Holds CONTROL SERVER and IMPERSONATE Rights

March 21, 2007
Pinal Dave
SQL Tips and Tricks
DBA, SQL Audit, SQL Login, SQL Server Security

Audit CONTROL SERVER and impersonation grants alongside sysadmin and role inheritance, test effective rights, and remove excess access.

Read More
SQL SERVER - SQL Commandments - Suggestions, Tips, Tricks

SQL SERVER – SQL Commandments – Suggestions, Tips, Tricks

March 20, 2007
Pinal Dave
SQL Performance
Best Practices, Database, Software Development, SQL Backup and Restore, SQL Constraint and Keys, SQL DateTime, SQL Download, SQL Error Messages, SQL Function, SQL Index, SQL Joins, SQL Server DBCC, SQL Server Security, SQL Stored Procedure

My 20 SQL Commandments for SQL Server, rewritten from an Oracle article: know your data, test with realistic data, write identical statements, and more tips.

Read More
SQL SERVER - Fix: Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize. hr = 0x80004005. SQLSTATE: 08001, Native Error: 17

SQL SERVER – Fix: Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize. hr = 0x80004005. SQLSTATE: 08001, Native Error: 17

March 16, 2007
Pinal Dave
SQL Tips and Tricks
SQL Error Messages, SQL Server Security, SQL Utility

A Sqllib error with hr = 0x80004005 and Native Error 17 says SQL Server does not exist or access denied. The simple fix is to enable TCP-IP in Configuration Manager.

Read More
SQL SERVER - DBCC command to RESEED Table Identity Value - Reset Table Identity

SQL SERVER – DBCC command to RESEED Table Identity Value – Reset Table Identity

March 15, 2007
Pinal Dave
SQL Performance
SQL Index, SQL Scripts, SQL Server DBCC, SQL Server Security

DBCC CHECKIDENT with RESEED lets you reset table identity to any value. Reseed to 0 so the next insert gets 1, and never go below values already in the table.

Read More
Cream and slate twine balls occupy two wicker baskets, a third stays empty, and a shared tray holds both colors

Showing Comma-Separated Role Members for Every Database Role

February 20, 2007
Pinal Dave
SQL Tips and Tricks
SQL Function, SQL Scripts, SQL Server, SQL Server Security

Comma-separated role members make direct assignments easier to review. The queries retain empty roles and label public membership as implicit. Keep the underlying rows because nested roles and directory groups need a separate effective-access review.

Read More
SQL SERVER - FIX : Error 15023: User already exists in current database.

SQL SERVER – FIX : Error 15023: User already exists in current database.

February 15, 2007
Pinal Dave
SQL Performance
DBA, SQL Cursor, SQL Download, SQL Error Messages, SQL Joins, SQL Scripts, SQL Server DBCC, SQL Server Security, SQL Stored Procedure

Error 15023: User already exists in current database. I fix it with sp_change_users_login, using Report, Auto_Fix or Update_One to link the user to a login.

Read More
Previous 1 … 53 54 55 56 57 Next
  • Books
  • Testimonials
  • Privacy Policy

© 2006 – 2026 All rights reserved. pinal @ SQLAuthority.com