Viewing 15 posts - 1,891 through 1,905 (of 2,897 total)
fpereiras (5/27/2009)
homebrew01 (5/27/2009)
fpereiras (5/26/2009)
Hi use sql authentication mode and personate user. The users are no trusted Unix and Windows.
Not quite sure what you mean.
Windows authentication works if I remote onto...
May 27, 2009 at 8:22 am
fpereiras (5/26/2009)
Hi use sql authentication mode and personate user. The users are no trusted Unix and Windows.
Not quite sure what you mean.
Windows authentication works if I remote onto 1 server,...
May 27, 2009 at 6:06 am
No I didn't test it in dev. It was a bit of a rush. Took a chance and added the column and updated it later with data. Got lucky and...
May 26, 2009 at 12:39 pm
Is your boss aware of the current problem doing the restore ? What does he say about it ?
Last I knew, you could not use Veritas to restore to...
May 19, 2009 at 9:35 am
And if you want a quick view of all your database sizes alphabetically:
IF OBJECT_ID('tempdb..#t') IS NOT NULL
DROP TABLE #dbsize
CREATE TABLE #dbsize
(DB_Name sysname
,size int)
--now load the temp table
INSERT INTO #dbsize
exec...
May 18, 2009 at 2:19 pm
Jeffrey Williams (4/27/2009)
May 15, 2009 at 12:42 pm
Use the GUI but don't save the changes. then generate the script to a new query window and it will build your T-SQL script for you.
May 14, 2009 at 8:45 am
I found this in my old SQL 2000 scripts and it will work in 2005. You could put the 2 sets of results to work tables and then compare them.
select...
May 13, 2009 at 7:18 pm
Would a transaction log backup be advisable now ? Then you can apply it (them) to your old full backup.
May 12, 2009 at 9:15 am
Thanks .... That looks like it should work, but I get "Argument data type int is invalid for argument 1 of substring function."
Maybe it doesn't like the columns being varchar...
May 6, 2009 at 12:28 pm
On the first day. You need disaster recovery in place for your developement area.
May 6, 2009 at 6:07 am
Alvin Ramard (5/5/2009)
Shrink tempdb? Who said tempdb was on that drive?
Since the OP didn't give us much info, we're left to speculate wildly to cover all possible scenarios.
May 5, 2009 at 1:41 pm
Ratheesh.K.Nair (5/5/2009)
Shrink the db having high log file size.
Check the temp DB, if its huge and ur server is not production then...
May 5, 2009 at 9:35 am
DTSRun /S ServerName /E /N"PackageName"
see: http://msdn.microsoft.com/en-us/library/aa224467(SQL.80).aspx
May 4, 2009 at 9:39 am
Viewing 15 posts - 1,891 through 1,905 (of 2,897 total)