Viewing 15 posts - 1,291 through 1,305 (of 1,335 total)
yes as told by the last user use DTS to transfer the jobs if u script out then use that remember to change the target server name parameter.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 19, 2007 at 3:39 am
this is called as hop problem in sql server. a very good article for the same is availble in this site just go through the link given below.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 19, 2007 at 3:31 am
whenever agent is started u will find a entry in the sysprocesses table with program_name like SQLAgent - Generic Refresher and not necessarily that your spid should...
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 18, 2007 at 5:30 am
specifying the retention period is available with 2005. There have been few may chages to the Mp wizard in sql 2005.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 18, 2007 at 5:21 am
i think its possible to get the last login details for connections that are alive in the server. we can use a join between the sysprocesses and syslogins tables to...
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 18, 2007 at 5:18 am
i think u have not updated the target server properties in the destination server. do that so that jobs will run fine.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 18, 2007 at 5:00 am
to check if agent service is running. check for the spid 51 in sysprocesses table and if that shows SQL Generic refresher that really menas ur agent service is running....
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 17, 2007 at 5:26 am
If we run Maintenance Plans for this database, the same thing happen.
what exactly is happening. is SQL occupying your whole of 8GB RAM. if so check the...
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 17, 2007 at 5:22 am
either set XACT_ABORT on in your connection or use set distributed transaction on so that u wil be able to call the sql w/o errors.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 17, 2007 at 5:19 am
use a domain accounjt itself and give proper sharing and ssecurity permissions for the user to that share. make sure if sql server can read that share using TSQL statements....
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 16, 2007 at 5:28 am
u directly can't omit the possibility of permissions problem. please check the permissions given for sql startup account. also if are very sure that its not a permission problem then...
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 16, 2007 at 5:24 am
its surely a permission problem. but also check for the permissions of the account starting ur sql server if its not local system.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 16, 2007 at 5:21 am
you have a option called restore with verify only which just verifies ur backup and does not restore the database. u can use that to verify ur backup thats made.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 14, 2007 at 8:39 am
whats the type of windows authentication mechanism being used. is it kerebros or NTLM if kerberos it mite be a hop problem. a good article for the same is available...
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 14, 2007 at 8:31 am
yes of course sa is with sysadmin privilege i thought that u had lost ur sa password and wanted to reset the same. if so u can login with windows...
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
January 14, 2007 at 8:23 am
Viewing 15 posts - 1,291 through 1,305 (of 1,335 total)