Viewing 15 posts - 196 through 210 (of 2,387 total)
You may try CASE statement like
ORDER BY
CASE WHEN @ColumnName='LastName' THEN LastName
WHEN @ColumnName='Salary' THEN CONVERT(varchar(50), Salary)
WHEN @ColumnName='SSN' THEN SSNEND
November 24, 2004 at 12:22 pm
1. Restore the full database with norecovery option.
2. Restore all log backups since the full backup with norecovery option until before you deleted the column.
3. Restore database with recovery option.
See...
November 24, 2004 at 9:44 am
No, You can't.
Do you have any full backup during last 20 months?
If you don't have, Try Lumigent Log Explorer for SQL Server http://www.lumigent.com/products/le_sql.html
November 24, 2004 at 9:23 am
My point is you may not even need a 40GB log file for the database. Set it auto grow with maxsize will prevent it to use all disk spaces. But...
November 24, 2004 at 8:06 am
Move SQL Server 7.0 database to 2000 is different than migrating 6.5 to 2000. Yes, you could use wizard but you also can do it by backup/restore or detach/attach the...
November 24, 2004 at 7:54 am
Your log file cound grow for many reasons. But you also can shrink it to a reasonable size bacause your database may not need such large log file. Run "dbcc...
November 24, 2004 at 7:51 am
Are you still in SQL Server 6.5?
November 23, 2004 at 2:39 pm
It could be very large depending on whether you backup the log which appends to backup log file or create new one each time you backup the log.
It backups the the...
November 23, 2004 at 2:30 pm
"My question is could I have resolved this error by updating the originating_server name in the msdb..sysjobs table?"
Yes, It resolves the problem. You need run sp_configure 'allow update', 1 before...
November 23, 2004 at 2:24 pm
Trt exec xp_cmdshell 'net send xxxxxx TEST' from QA.
I suspect the issue comes from the permission of xp_cmdshell.
November 23, 2004 at 2:19 pm
Or did you restore with norecovery option? Check SQL Server errorlog, If you see message "Bypassing recovery for database 'xxx' because it is marked IN LOAD", Try restore the database...
November 23, 2004 at 12:11 pm
November 23, 2004 at 8:57 am
Check logging tab in your package property to see whether you have assign correct file path for error handing.
November 23, 2004 at 8:51 am
Use client network library (C:\WINNT\system32\cliconfg.exe) to set the TCP/IP as preferred protocol.
November 19, 2004 at 7:23 am
Viewing 15 posts - 196 through 210 (of 2,387 total)