Viewing 15 posts - 796 through 810 (of 1,365 total)
The IDENTITY property and the column it's attached to are inseparable, which means that you can't add or remove IDENTITY from an existing column.You can use workarounds, but these can...
January 6, 2009 at 7:42 am
Why don't you try by specifying the same 'sa' password tht worked with first named installation and change it later.
MJ
January 6, 2009 at 7:16 am
January 6, 2009 at 6:35 am
For object level permissions, replace testing with the username you want to script out permissions:-
SET NOCOUNT ON
-- declare all variables
DECLARE @DBName SYSNAME
DECLARE @sql nvarchar(max)
DECLARE @sSQL1 Varchar(30)
DECLARE @iRowCount ...
January 6, 2009 at 6:33 am
Use the below mentioned stored procedure and replace test2 with the required loginname.
Create PROC usp_sql_audit
AS
SET NOCOUNT ON
IF EXISTS (SELECT * FROM tempdb.dbo.sysobjects WHERE name = '##Users' AND type in (N'U'))
DROP...
January 6, 2009 at 5:21 am
There is no such useful table. However, you can use profiler to track the activity against sql server database and then make an conclusion as to which procedures were never...
January 5, 2009 at 6:11 pm
select * from sys.columns
where name=''
go
select * from information_schema.columns
where column_name=''
MJ
January 5, 2009 at 3:46 pm
From BOL:
Point-in-time recovery is not supported with the Bulk-Logged Recovery model. Bulk-Logged recovery only allows the database to be recovered to the end of a transaction log backup when the...
January 5, 2009 at 1:04 pm
Change condition to where Table Name = Upper(Name) and then evaluate the policy against your database.
MJ
January 4, 2009 at 7:30 am
sunny Brook (1/2/2009)
1. add 1 new filegroups
2. add a file to the filegroup
3. Alter your partition scheme to include the added new...
January 2, 2009 at 1:52 pm
No problem with that but as a best practice try not to shrink databases.
MJ
January 2, 2009 at 12:30 pm
I don't think its possible using sql server native tables. Third party utilities might help here.
MJ
January 2, 2009 at 6:01 am
From books online:
ON { | filegroup | "default" }
Specifies the partition scheme or filegroup on which the table is stored. If . If filegroup is specified,...
January 2, 2009 at 5:58 am
I suspect it has something to do with FAST switch used here.
FAST
Specifies whether to perform a fast scan of the index and output minimal information. A fast scan does...
January 2, 2009 at 5:34 am
I created one test login and granted no other permission except default one. After that I ran your code and it ran perfectly fine.
Microsoft SQL Server 2005 - 9.00.3042.00
MJ
January 2, 2009 at 5:29 am
Viewing 15 posts - 796 through 810 (of 1,365 total)