Viewing 15 posts - 511 through 525 (of 1,335 total)
Post the error message that you get when you fire the alter db syntax.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 3:42 am
URL for the article.
http://www.sqlservercentral.com/columnists/jDave/3046.asp
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 3:40 am
Database Monitoring is a Disaster Recovery solution where by your database can be put up in a secondary server and can be used when the primary server loses connection. DB...
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 3:39 am
You would need to give access to other user databases as permission needs. the second part of your question is not clear. can you post briefly.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 3:28 am
This error occcurs when databases with different collation interacts. This can be solved by specifying the collate collation name in the from clause of your query.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 3:13 am
Script the index and the fire against the destination table before that remember to change the tablename in the script generated.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 2:35 am
You can use read committed isolation level so that you don't get uncommitted data as a result.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 2:08 am
Check if this post given below helps you.
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=146&messageid=362688
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 2:05 am
Are you mentioning any delimiters in moving data.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 2:03 am
Sure i shall do that.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 1:58 am
This looks funny. you are posting a question on how to post a question. Just post a question like how you have done now and post it in the right...
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 1:31 am
Check setting isolation levels appropriate so that deadlocks and locks can be avoided.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 12:27 am
dbcreator role should be the one you should give if you give sysadmin then the users cando anything with sql server so better avoid that.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 12:19 am
use
backup log dbname with truncate_only
go
dbcc shrinkfile(2,targetsize)
this should shrink logfile for you.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 12:15 am
Recovery model full is the best option to backup tlogs. If you dont want to lose much data then backup tlogs every 5 or 10 mins and have a retaination...
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 17, 2007 at 12:13 am
Viewing 15 posts - 511 through 525 (of 1,335 total)