Showing posts with label process. Show all posts
Showing posts with label process. Show all posts

Sunday, March 11, 2012

Cannot view database properties

Hello all....

I am in the process of changing all of the collation to SQL_Latin1_General_CP1_CI_AS.

I have backed up all databases, and uninstalled SQL Server 2005. I then reinstalled SQL Server 2005, setting the server collation to SQL_Latin1_General_CP1_CI_AS.

The user databases have been restored and are accessible by all applications.

If I try to view the properties of any database (system or user), I get the following error:

*********************************************************************************************************************************

TITLE: Microsoft SQL Server Management Studio

Cannot show requested dialog.


ADDITIONAL INFORMATION:

Cannot show requested dialog. (SqlMgmt)

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AI" in the equal to operation. (Microsoft SQL Server, Error: 468)

****************************************************************************************************************************************

I have tried executing the "Alter Database [dbname] Collate SQL_Latin1_General_CP1_CI_AS" procedure, but that does seem to help. Does anyone have any ideas?

Thanks,

Forch

What is the collation or all the databases?

run select * from sys.databases.

How did you restore the databases, backup/restore, attach/dettach?

|||

Master is SQL_Latin1_General_CP_C1_AS, and the rest of the system dbs is Latin1_General_CI_AI. The user dbs are evenly divided between the 2.

I can't remember how I restored.... it was probably backup / restore.

Thanks,

Forch

|||

Hi Forch,

Probably the backed up databases have the old collation, but the SQL server system databases have the new collation.

You can do:

ALTER RESTORED_DATABASE { COLLATE SQL_Latin1_General_CP1_CI_AScollation_name }

to change the collation of the restored databases to the new collation

Cheers

|||Have you tried to access the database from the query analyzer too?

Cannot view database properties

Hello all....

I am in the process of changing all of the collation to SQL_Latin1_General_CP1_CI_AS.

I have backed up all databases, and uninstalled SQL Server 2005. I then reinstalled SQL Server 2005, setting the server collation to SQL_Latin1_General_CP1_CI_AS.

The user databases have been restored and are accessible by all applications.

If I try to view the properties of any database (system or user), I get the following error:

*********************************************************************************************************************************

TITLE: Microsoft SQL Server Management Studio

Cannot show requested dialog.


ADDITIONAL INFORMATION:

Cannot show requested dialog. (SqlMgmt)

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AI" in the equal to operation. (Microsoft SQL Server, Error: 468)

****************************************************************************************************************************************

I have tried executing the "Alter Database [dbname] Collate SQL_Latin1_General_CP1_CI_AS" procedure, but that does seem to help. Does anyone have any ideas?

Thanks,

Forch

What is the collation or all the databases?

run select * from sys.databases.

How did you restore the databases, backup/restore, attach/dettach?

|||

Master is SQL_Latin1_General_CP_C1_AS, and the rest of the system dbs is Latin1_General_CI_AI. The user dbs are evenly divided between the 2.

I can't remember how I restored.... it was probably backup / restore.

Thanks,

Forch

|||

Hi Forch,

Probably the backed up databases have the old collation, but the SQL server system databases have the new collation.

You can do:

ALTER RESTORED_DATABASE { COLLATE SQL_Latin1_General_CP1_CI_AScollation_name }

to change the collation of the restored databases to the new collation

Cheers

|||Have you tried to access the database from the query analyzer too?

Thursday, March 8, 2012

Cannot update record through vb or Enterprise manager

When trying to update a specific row in a table an error
occurs.
[Microsoft][ODBC SQL SERVER DRIVER][SQL SERVER]
SQLDumExceptionhandler. Process 51 generated fatal
exception c0000005 ACCEPTION_ACCESS_VIOLATION. SQL Server
is terminating this process.
What could be the reason for this? There are no relations
hips or constraints on and between any tables.
What build of SQL Server is it ? Would suggest
I would run DBCC CHECKDB to check for corruption / specifically DBCC
CHECKTABLE on the table being queried
I would then look at the last SQL Server Errorlog when it happened and see
if there are any matches on http://www.microsoft.com/support for kb's that
have a similar pattern ie on the Short Stack Dump info reported. Below is
an example - so if you had this output I would search the kb and google
(groups and web) for Fill6Xdata . Be aware that some of the function calls
are quite generic so watch out for false positives.
Ideally you should open a case with PSS
-
Short Stack Dump
0069EF5F Module(sqlservr+0029EF5F) (Fill6xData(unsigned char *,class
CXVariant *,class CTypeInfo const *,unsigned long *)+0000009A)
0069BEDE Module(sqlservr+0029BEDE) (intnl_paramdata(struct srv_proc
*,int)+000000DB)
regards,
Andy.
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:249c701c46020$9cdb8a70$a601280a@.phx.gbl...
> When trying to update a specific row in a table an error
> occurs.
> [Microsoft][ODBC SQL SERVER DRIVER][SQL SERVER]
> SQLDumExceptionhandler. Process 51 generated fatal
> exception c0000005 ACCEPTION_ACCESS_VIOLATION. SQL Server
> is terminating this process.
> What could be the reason for this? There are no relations
> hips or constraints on and between any tables.

Wednesday, March 7, 2012

cannot stop SQL Server 2005 Service.

Hello,

My problem is,

I cannot stop SQL Server 2005 Service.

after "net stop sqlserver", not stop for all time.

but, I can kill process from task manager.

How can I fix this probelm ?

Environment:

OS: Windows XP SP 2

DB: SQL Server 2005 SP2, SQL Server 2005 SP2 Express Edition.

Regards,

Yoshihiro Kawabata

are you able to stop it from the services snap in?|||

Try "net stop mssqlserver /y" for default instance or "net stop mssql$<instance_name> /y" for named instance. This will force terminating any child process first before terminating sqlserver.

|||NO, I cannot stop services by Management Studio and Configuration Manager.|||

Thanks

But, I cannot stop services by 'net stop "sql server (sqlexpress)" /y '.

|||

what is the error msg u gets... is there any entry in log... is the loged in user is a privilaged user to do this... and also check you have local instance of sql server...

Madhu

|||

The correct syntax is:

net stop mssql$sqlexpress /y

Sunday, February 12, 2012

Cannot run job created by SMO

I've create a SQL Agent job using C# SMO to process an Analysis Service Database (see code below). When I tried to start job from Management Studio, I get the following error message...any ideas?

TITLE: Microsoft.SqlServer.Smo

Start failed for Job 'Schedule Job OLAPProj'.

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1314.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Start+Job&LinkId=20476


ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Cannot start the job "Schedule Job OLAPProj" (ID 089BEE15-B060-466E-B59E-7F7DAB1EB8DB) because it does not have any job server or servers defined. Associate the job with a job server by calling sp_add_jobserver. (Microsoft SQL Server, Error: 14256)



Common.ServerConnection l_oServerConn = new Common.ServerConnection();

l_oServerConn.ServerInstance = txtServer.Text;

l_oServerConn.LoginSecure = true;

l_oServerConn.Connect();

Smo.Server l_oServer = new Smo.Server(l_oServerConn);

Agent.Job l_oJob = new Agent.Job(l_oServer.JobServer, "Schedule Job " + cboDB.Text);

l_oJob.IsEnabled = true;

l_oJob.Description = "Schedule Job Processing OLAP Cube: " + cboDB.Text;

l_oJob.OwnerLoginName = @."NT AUTHORITY\SYSTEM";

l_oJob.Create();

Agent.JobStep l_oJobStep = new Agent.JobStep(l_oJob, "Process " + cboDB.Text);

l_oJobStep.SubSystem = Agent.AgentSubSystem.AnalysisCommand;

string l_sCmd = @."<Process xmlns=""http://schemas.microsoft.com/analysisservices/2003/engine"">";

l_sCmd = l_sCmd + "<Object><DatabaseID>" + cboDB.Text + "</DatabaseID></Object><Type>ProcessFull</Type>";

l_sCmd = l_sCmd + "<WriteBackTableCreation>UseExisting</WriteBackTableCreation></Process>";

l_oJobStep.Command = l_sCmd;

l_oJobStep.Server = txtServer.Text;

l_oJobStep.DatabaseName = @."master";

l_oJobStep.JobStepFlags = Agent.JobStepFlags.AppendToJobHistory;

l_oJobStep.OnSuccessAction = Agent.StepCompletionAction.QuitWithSuccess;

l_oJobStep.OnFailAction = Agent.StepCompletionAction.QuitWithFailure;

l_oJobStep.Create();


I have posted a sample here, which should clarify this. Please let me know if you have further issues after reading the sample.

|||Based on your sample, I've added the following which seemed to do the trick:

l_oJob.ApplyToTargetServer("(local)");

Initially I use "localhost\yukon" which is name of my instance but that failed and "(local)" worked. Thanks.