Hi,
I am doing a tuning exercise on a SQL 2K5 instance, I am encountering
a problem when Profiler goes to create a table. I have profiled
Profiler and have extracted the following code
CREATE TABLE [dbo].[con1] ([RowNumber] int IDENTITY(0,1) PRIMARY KEY,
[EventClass] int NULL,[Duration] bigint NULL,,
[TextData] ntext NULL,[SPID] int NULL,[BinaryData] image NULL,[CPU]
int NULL,[Reads] bigint NULL,[Writes] bigint NULL,[ApplicationName]
nvarchar(128) NULL,[ClientProcessID] int NULL,[DatabaseID] int NULL,
[DatabaseName] nvarchar(128) NULL,[EventSequence] int NULL,
[EventSubClass] int NULL,[HostName] nvarchar(128) NULL,[IntegerData]
int NULL,[IsSystem] int NULL,[LoginName] nvarchar(128) NULL,[LoginSid]
image NULL,[NTDomainName] nvarchar(128) NULL,[NTUserName]
nvarchar(128) NULL,[RequestID] int NULL,[ServerName] nvarchar(128)
NULL,[SessionLoginName] nvarchar(128) NULL,[StartTime] datetime NULL,
[TransactionID] bigint NULL)
As you can see, after Duration (the 3rd column), there is a double
comma inserted which of course is erroring.
This occurs when defining a table to save to prior to running the
trace, and defining a table after running the trace.
I have tried the standard profiler which appears to work fine.
I also updated to SP2 CTP (this is a test server) because it appeared
to be an issue simular to this http://support.microsoft.com/?
kbid=925335.
A quick response would be appreciated as I am a contractor and I am on
tight timescales.
Cheers
Steve
Steve,
I don't know how to fix the error with profiler but I recommend you not do
that in the fist place. Tracing to a table can be a huge performance hit and
can skew your results. It is recommended that you trace directly to a file
using sp_trace_create and then use fn_trace_gettable to retrieve the data.
You can do something like this to put the trace results in a table:
SELECT * INTO YourTable FROM fn_trace_gettable(xxx)
If you already have a trace in profiler you can save it to a file and do the
same.
Andrew J. Kelly SQL MVP
"Steve L" <steve_lawrenson@.tiscali.co.uk> wrote in message
news:1170411376.241148.280690@.v33g2000cwv.googlegr oups.com...
> Hi,
> I am doing a tuning exercise on a SQL 2K5 instance, I am encountering
> a problem when Profiler goes to create a table. I have profiled
> Profiler and have extracted the following code
> CREATE TABLE [dbo].[con1] ([RowNumber] int IDENTITY(0,1) PRIMARY KEY,
> [EventClass] int NULL,[Duration] bigint NULL,,
> [TextData] ntext NULL,[SPID] int NULL,[BinaryData] image NULL,[CPU]
> int NULL,[Reads] bigint NULL,[Writes] bigint NULL,[ApplicationName]
> nvarchar(128) NULL,[ClientProcessID] int NULL,[DatabaseID] int NULL,
> [DatabaseName] nvarchar(128) NULL,[EventSequence] int NULL,
> [EventSubClass] int NULL,[HostName] nvarchar(128) NULL,[IntegerData]
> int NULL,[IsSystem] int NULL,[LoginName] nvarchar(128) NULL,[LoginSid]
> image NULL,[NTDomainName] nvarchar(128) NULL,[NTUserName]
> nvarchar(128) NULL,[RequestID] int NULL,[ServerName] nvarchar(128)
> NULL,[SessionLoginName] nvarchar(128) NULL,[StartTime] datetime NULL,
> [TransactionID] bigint NULL)
> As you can see, after Duration (the 3rd column), there is a double
> comma inserted which of course is erroring.
> This occurs when defining a table to save to prior to running the
> trace, and defining a table after running the trace.
> I have tried the standard profiler which appears to work fine.
> I also updated to SP2 CTP (this is a test server) because it appeared
> to be an issue simular to this http://support.microsoft.com/?
> kbid=925335.
> A quick response would be appreciated as I am a contractor and I am on
> tight timescales.
> Cheers
> Steve
>
|||On 2 Feb, 14:11, "Andrew J. Kelly" <sqlmvpnooos...@.shadhawk.com>
wrote:
> Steve,
> I don't know how to fix the error with profiler but I recommend you not do
> that in the fist place. Tracing to a table can be a huge performance hit and
> can skew your results. It is recommended that you trace directly to a file
> using sp_trace_create and then use fn_trace_gettable to retrieve the data.
> You can do something like this to put the trace results in a table:
> SELECT * INTO YourTable FROM fn_trace_gettable(xxx)
> If you already have a trace in profiler you can save it to a file and do the
> same.
> --
> Andrew J. Kelly SQL MVP
> "Steve L" <steve_lawren...@.tiscali.co.uk> wrote in message
> news:1170411376.241148.280690@.v33g2000cwv.googlegr oups.com...
>
>
>
>
>
>
> - Show quoted text -
Hi Andrew
thanks for the response, I will use the method above as a workaround
and thanks for that information. It would be nice to know if this is a
recognised issue by MS and what their recommended workarounds are for
it.
Cheers
Steve L
Showing posts with label create. Show all posts
Showing posts with label create. Show all posts
Thursday, March 29, 2012
Error when trying to create new SQL Server login via ado.Net
I get an error when I try to execute the following code using ADO.Net
in VB.Net:
conn.open
sqlString="CREATE LOGIN test WITH PASSWORD = '1qaz2wsx'"
command=new SqlCommand(sqlString)
command.connection = conn
command.ExecuteNonQuery()
The error occurs when executing the ExecuteNonQuery line and is:
"Line1: Incorrect syntax near 'LOGIN' "
The database connection is connected to the master database of SQL 2005
Express using the sa account. This line executes just fine in Sql
Server Studio Manger when connected as sa. Am I not allowed to create
database logins via ado.net?!?! I need to for my application.
Thx,
MarcusHi
It seems to be something wrong with quoatations. Print the sqlString and see
if you can execute it in QA
"holysmokes99" <holysmokes99@.hotmail.com> wrote in message
news:1143588567.138045.218660@.j33g2000cwa.googlegroups.com...
>I get an error when I try to execute the following code using ADO.Net
> in VB.Net:
> conn.open
> sqlString="CREATE LOGIN test WITH PASSWORD = '1qaz2wsx'"
> command=new SqlCommand(sqlString)
> command.connection = conn
> command.ExecuteNonQuery()
> The error occurs when executing the ExecuteNonQuery line and is:
> "Line1: Incorrect syntax near 'LOGIN' "
> The database connection is connected to the master database of SQL 2005
> Express using the sa account. This line executes just fine in Sql
> Server Studio Manger when connected as sa. Am I not allowed to create
> database logins via ado.net?!?! I need to for my application.
> Thx,
> Marcus
>|||I suggest you double check your connection string to make sure you are
connected to the SQL Express instance since this message indicates you are
connected to a pre-SQL 2000 instance. You can insert code like the example
below to query the instance version. My SQL Express instance returns
"9.00.1399.06".
command=new SqlCommand("SELECT SERVERPROPERTY('ProductVersion')")
Dim version as String = command.ExecuteScalar().ToString()
MessageBox.Show(version)
Hope this helps.
Dan Guzman
SQL Server MVP
"holysmokes99" <holysmokes99@.hotmail.com> wrote in message
news:1143588567.138045.218660@.j33g2000cwa.googlegroups.com...
>I get an error when I try to execute the following code using ADO.Net
> in VB.Net:
> conn.open
> sqlString="CREATE LOGIN test WITH PASSWORD = '1qaz2wsx'"
> command=new SqlCommand(sqlString)
> command.connection = conn
> command.ExecuteNonQuery()
> The error occurs when executing the ExecuteNonQuery line and is:
> "Line1: Incorrect syntax near 'LOGIN' "
> The database connection is connected to the master database of SQL 2005
> Express using the sa account. This line executes just fine in Sql
> Server Studio Manger when connected as sa. Am I not allowed to create
> database logins via ado.net?!?! I need to for my application.
> Thx,
> Marcus
>|||> It seems to be something wrong with quoatations. Print the sqlString and
> see if you can execute it in QA
No need to print the SQL statement here since it is in clear text in Marcus'
code snippet:
CREATE LOGIN test WITH PASSWORD = '1qaz2wsx'
Hope this helps.
Dan Guzman
SQL Server MVP
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eVeLQavUGHA.4436@.TK2MSFTNGP10.phx.gbl...
> Hi
> It seems to be something wrong with quoatations. Print the sqlString and
> see if you can execute it in QA
>
> "holysmokes99" <holysmokes99@.hotmail.com> wrote in message
> news:1143588567.138045.218660@.j33g2000cwa.googlegroups.com...
>|||Hi,Dan
Yep, I got it. thanks
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:uahPs5yUGHA.5900@.tk2msftngp13.phx.gbl...
> No need to print the SQL statement here since it is in clear text in
> Marcus' code snippet:
> CREATE LOGIN test WITH PASSWORD = '1qaz2wsx'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:eVeLQavUGHA.4436@.TK2MSFTNGP10.phx.gbl...
>|||Oh, Jeesh, My bad!!! Dan you were spot on. I was connecting to an
instance of SQL Server 2000, and not Express. I have both on my machine
and forgot to reference it as "Marcus\SQLEXPRESS", instead using
"Marcus" only. CREATE LOGIN is new for SQL Server 2005 and thus I got a
syntax error when connecting to SQL 2000. Thanks for your insight.
On a sort-of-related note, is there a way for me to iterate through all
the SQL Server Express instances on the network? Using SQL-DMO, the
code below gives me the names of the servers, but some of the SQL
Express servers are named "[server_name]\SQLEXPRESS", while others are
just "[server_name]" (even though they do not have anything other that
SQL Express on them). If they were all suffixed with "SQLEXPRESS" then
that would be easy, but it doesn't seem to work that way.
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Dim oNames As SQLDMO.NameList
Dim oSQLApp As SQLDMO.Application
Dim oServer As SQLDMO.SQLServer2
oSQLApp = New SQLDMO.Application
oNames = oSQLApp.ListAvailableSQLServers
For i As Integer = 1 To oNames.Count
TextBox1.AppendText(oNames.Item(i) + Environment.NewLine)
Next
End sub
Thanks!
Marcus|||Check the following:
1) SQL Brower service is enabled and running
2) Port 1434 isn't blocked (e.g. Windows firewall)
3) The SQL Express instance is configured for remote connections
Hope this helps.
Dan Guzman
SQL Server MVP
"Marcus" <holysmokes99@.hotmail.com> wrote in message
news:1143659183.191249.143360@.e56g2000cwe.googlegroups.com...
> Oh, Jeesh, My bad!!! Dan you were spot on. I was connecting to an
> instance of SQL Server 2000, and not Express. I have both on my machine
> and forgot to reference it as "Marcus\SQLEXPRESS", instead using
> "Marcus" only. CREATE LOGIN is new for SQL Server 2005 and thus I got a
> syntax error when connecting to SQL 2000. Thanks for your insight.
> On a sort-of-related note, is there a way for me to iterate through all
> the SQL Server Express instances on the network? Using SQL-DMO, the
> code below gives me the names of the servers, but some of the SQL
> Express servers are named "[server_name]\SQLEXPRESS", while others are
> just "[server_name]" (even though they do not have anything other that
> SQL Express on them). If they were all suffixed with "SQLEXPRESS" then
> that would be easy, but it doesn't seem to work that way.
> Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
> System.EventArgs) Handles Button2.Click
> Dim oNames As SQLDMO.NameList
> Dim oSQLApp As SQLDMO.Application
> Dim oServer As SQLDMO.SQLServer2
> oSQLApp = New SQLDMO.Application
> oNames = oSQLApp.ListAvailableSQLServers
> For i As Integer = 1 To oNames.Count
> TextBox1.AppendText(oNames.Item(i) + Environment.NewLine)
> Next
> End sub
>
> Thanks!
> Marcus
>|||Thanks, Dan. You were right again. On the machine with SQL Express
only, Windows Firewall was on. When I disabled it, the server name and
sql server instancen name came up when I ran the code above, i.e.
"training\sqlexpress", not just the server name as before when firewall
was active. Why did the server name come up at all then when the
firewall was enabled, when using the SQL-DMO code above?
Cheers,
Marcus|||> Why did the server name come up at all then when the
> firewall was enabled, when using the SQL-DMO code above?
IIRC, before SQL Server 2000, network broadcast packets sent to facilitate
server enumeration. According to Perter's blog
(http://blogs.msdn.com/sql_protocols.../24/473502.aspx), legacy
behavior can show default instances even with UDP 1434 blocked.
Hope this helps.
Dan Guzman
SQL Server MVP
"Marcus" <holysmokes99@.hotmail.com> wrote in message
news:1143736505.471840.78380@.i39g2000cwa.googlegroups.com...
> Thanks, Dan. You were right again. On the machine with SQL Express
> only, Windows Firewall was on. When I disabled it, the server name and
> sql server instancen name came up when I ran the code above, i.e.
> "training\sqlexpress", not just the server name as before when firewall
> was active. Why did the server name come up at all then when the
> firewall was enabled, when using the SQL-DMO code above?
> Cheers,
> Marcus
>sql
in VB.Net:
conn.open
sqlString="CREATE LOGIN test WITH PASSWORD = '1qaz2wsx'"
command=new SqlCommand(sqlString)
command.connection = conn
command.ExecuteNonQuery()
The error occurs when executing the ExecuteNonQuery line and is:
"Line1: Incorrect syntax near 'LOGIN' "
The database connection is connected to the master database of SQL 2005
Express using the sa account. This line executes just fine in Sql
Server Studio Manger when connected as sa. Am I not allowed to create
database logins via ado.net?!?! I need to for my application.
Thx,
MarcusHi
It seems to be something wrong with quoatations. Print the sqlString and see
if you can execute it in QA
"holysmokes99" <holysmokes99@.hotmail.com> wrote in message
news:1143588567.138045.218660@.j33g2000cwa.googlegroups.com...
>I get an error when I try to execute the following code using ADO.Net
> in VB.Net:
> conn.open
> sqlString="CREATE LOGIN test WITH PASSWORD = '1qaz2wsx'"
> command=new SqlCommand(sqlString)
> command.connection = conn
> command.ExecuteNonQuery()
> The error occurs when executing the ExecuteNonQuery line and is:
> "Line1: Incorrect syntax near 'LOGIN' "
> The database connection is connected to the master database of SQL 2005
> Express using the sa account. This line executes just fine in Sql
> Server Studio Manger when connected as sa. Am I not allowed to create
> database logins via ado.net?!?! I need to for my application.
> Thx,
> Marcus
>|||I suggest you double check your connection string to make sure you are
connected to the SQL Express instance since this message indicates you are
connected to a pre-SQL 2000 instance. You can insert code like the example
below to query the instance version. My SQL Express instance returns
"9.00.1399.06".
command=new SqlCommand("SELECT SERVERPROPERTY('ProductVersion')")
Dim version as String = command.ExecuteScalar().ToString()
MessageBox.Show(version)
Hope this helps.
Dan Guzman
SQL Server MVP
"holysmokes99" <holysmokes99@.hotmail.com> wrote in message
news:1143588567.138045.218660@.j33g2000cwa.googlegroups.com...
>I get an error when I try to execute the following code using ADO.Net
> in VB.Net:
> conn.open
> sqlString="CREATE LOGIN test WITH PASSWORD = '1qaz2wsx'"
> command=new SqlCommand(sqlString)
> command.connection = conn
> command.ExecuteNonQuery()
> The error occurs when executing the ExecuteNonQuery line and is:
> "Line1: Incorrect syntax near 'LOGIN' "
> The database connection is connected to the master database of SQL 2005
> Express using the sa account. This line executes just fine in Sql
> Server Studio Manger when connected as sa. Am I not allowed to create
> database logins via ado.net?!?! I need to for my application.
> Thx,
> Marcus
>|||> It seems to be something wrong with quoatations. Print the sqlString and
> see if you can execute it in QA
No need to print the SQL statement here since it is in clear text in Marcus'
code snippet:
CREATE LOGIN test WITH PASSWORD = '1qaz2wsx'
Hope this helps.
Dan Guzman
SQL Server MVP
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eVeLQavUGHA.4436@.TK2MSFTNGP10.phx.gbl...
> Hi
> It seems to be something wrong with quoatations. Print the sqlString and
> see if you can execute it in QA
>
> "holysmokes99" <holysmokes99@.hotmail.com> wrote in message
> news:1143588567.138045.218660@.j33g2000cwa.googlegroups.com...
>|||Hi,Dan
Yep, I got it. thanks
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:uahPs5yUGHA.5900@.tk2msftngp13.phx.gbl...
> No need to print the SQL statement here since it is in clear text in
> Marcus' code snippet:
> CREATE LOGIN test WITH PASSWORD = '1qaz2wsx'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:eVeLQavUGHA.4436@.TK2MSFTNGP10.phx.gbl...
>|||Oh, Jeesh, My bad!!! Dan you were spot on. I was connecting to an
instance of SQL Server 2000, and not Express. I have both on my machine
and forgot to reference it as "Marcus\SQLEXPRESS", instead using
"Marcus" only. CREATE LOGIN is new for SQL Server 2005 and thus I got a
syntax error when connecting to SQL 2000. Thanks for your insight.
On a sort-of-related note, is there a way for me to iterate through all
the SQL Server Express instances on the network? Using SQL-DMO, the
code below gives me the names of the servers, but some of the SQL
Express servers are named "[server_name]\SQLEXPRESS", while others are
just "[server_name]" (even though they do not have anything other that
SQL Express on them). If they were all suffixed with "SQLEXPRESS" then
that would be easy, but it doesn't seem to work that way.
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Dim oNames As SQLDMO.NameList
Dim oSQLApp As SQLDMO.Application
Dim oServer As SQLDMO.SQLServer2
oSQLApp = New SQLDMO.Application
oNames = oSQLApp.ListAvailableSQLServers
For i As Integer = 1 To oNames.Count
TextBox1.AppendText(oNames.Item(i) + Environment.NewLine)
Next
End sub
Thanks!
Marcus|||Check the following:
1) SQL Brower service is enabled and running
2) Port 1434 isn't blocked (e.g. Windows firewall)
3) The SQL Express instance is configured for remote connections
Hope this helps.
Dan Guzman
SQL Server MVP
"Marcus" <holysmokes99@.hotmail.com> wrote in message
news:1143659183.191249.143360@.e56g2000cwe.googlegroups.com...
> Oh, Jeesh, My bad!!! Dan you were spot on. I was connecting to an
> instance of SQL Server 2000, and not Express. I have both on my machine
> and forgot to reference it as "Marcus\SQLEXPRESS", instead using
> "Marcus" only. CREATE LOGIN is new for SQL Server 2005 and thus I got a
> syntax error when connecting to SQL 2000. Thanks for your insight.
> On a sort-of-related note, is there a way for me to iterate through all
> the SQL Server Express instances on the network? Using SQL-DMO, the
> code below gives me the names of the servers, but some of the SQL
> Express servers are named "[server_name]\SQLEXPRESS", while others are
> just "[server_name]" (even though they do not have anything other that
> SQL Express on them). If they were all suffixed with "SQLEXPRESS" then
> that would be easy, but it doesn't seem to work that way.
> Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
> System.EventArgs) Handles Button2.Click
> Dim oNames As SQLDMO.NameList
> Dim oSQLApp As SQLDMO.Application
> Dim oServer As SQLDMO.SQLServer2
> oSQLApp = New SQLDMO.Application
> oNames = oSQLApp.ListAvailableSQLServers
> For i As Integer = 1 To oNames.Count
> TextBox1.AppendText(oNames.Item(i) + Environment.NewLine)
> Next
> End sub
>
> Thanks!
> Marcus
>|||Thanks, Dan. You were right again. On the machine with SQL Express
only, Windows Firewall was on. When I disabled it, the server name and
sql server instancen name came up when I ran the code above, i.e.
"training\sqlexpress", not just the server name as before when firewall
was active. Why did the server name come up at all then when the
firewall was enabled, when using the SQL-DMO code above?
Cheers,
Marcus|||> Why did the server name come up at all then when the
> firewall was enabled, when using the SQL-DMO code above?
IIRC, before SQL Server 2000, network broadcast packets sent to facilitate
server enumeration. According to Perter's blog
(http://blogs.msdn.com/sql_protocols.../24/473502.aspx), legacy
behavior can show default instances even with UDP 1434 blocked.
Hope this helps.
Dan Guzman
SQL Server MVP
"Marcus" <holysmokes99@.hotmail.com> wrote in message
news:1143736505.471840.78380@.i39g2000cwa.googlegroups.com...
> Thanks, Dan. You were right again. On the machine with SQL Express
> only, Windows Firewall was on. When I disabled it, the server name and
> sql server instancen name came up when I ran the code above, i.e.
> "training\sqlexpress", not just the server name as before when firewall
> was active. Why did the server name come up at all then when the
> firewall was enabled, when using the SQL-DMO code above?
> Cheers,
> Marcus
>sql
Tuesday, March 27, 2012
Error when trying to create new databaase using SQL Server
Hi,
I have installed MS SQL server and I'm trying to create a database using the Web Matrix Project. I'm doing the following:
1. Click the Data tab in the Workspace pane.
2. Click on "Add Database Connection"
3. Select "SQL Server/MSDE Database" and click OK
4. Enter the following information:
server=localhost
Windows authentication is on
Database=somename
Click Ok
After I do all this, I get the following error:
Unable to connect to the database
SQL server does not exist or access denied.
ConnectionOpen (Connect()).
The SQL Service Manager is running with the option "Distributed Transaction Coordinator" displaying on Services. (I'm new to SQL server).
What could be causing this to happen?
Thanks a lot."Add Database Connection" is for connecting to an existing database...
use SQL Enterprise Manager to create the database first.|||1. Check if the DNS entries for the database servers are correct. These could be one of the reasons.
2. You must also see if you have sysadmin previledges to create a database.
These are some of the points that come to mind.
Error when trying to create maintenance plans
I've an issue when trying to create maintenance plans on the management studio (new one or using the wizard)
I Received the Folowwing error:
Exception has been thrown by the target of an invocation. (mscorlib)
Additional information:
An OLE DB error 0x80004005 (Client unable to stablish connection) occurred while enumerating packages. A SQL statement issued and failed.
An OLE DB error 0x80004005 (Client unable to stablish connection) occurred while enumerating packages. A SQL statement issued and failed.
There is no service pack installed on the server.
Any help will be greatly appreciated.
Thanks in advance for the help.
Regards.
Hello Frivas,
I have a few questions that I hope will help narrow down your issue.
- Are you running SQL 2005 RTM, SP1 or SP2? I presume 2005 RTM since you said there is no service pack installed on the server, although perhaps you mean Windows service packs?
- When does the error occur? At the end of the wizard, at the end of saving the maintenance plan in the Designer UI? Or somewhere in the process?
- Does the login you're using to connect to the SQL Server have the sysadmin role, or some other roles?
- If the error dialog that comes up includes the small icon for additional details, can you please reproduce the problem and copy and paste the stack trace here?
James
|||..In addition to above I would like to know what is the reason for not having any service packs. You may know that SP2 has all the latest fixes for maintenance plans & ssis issue in this regard. http://download.microsoft.com/download/2/b/5/2b5e5d37-9b17-423d-bc8f-b11ecd4195b4/ReadmeSQL2005SP2.htm fyi.|||I don't understand what is the use of these kind of replys. If you don't know the answer just shut the mouth. Looks like just writing something to increase number of posts.
Everybody working in this field know the importance of installing the service packs.
Error when trying to create maintenance plans
I've an issue when trying to create maintenance plans on the management studio (new one or using the wizard)
I Received the Folowwing error:
Exception has been thrown by the target of an invocation. (mscorlib)
Additional information:
An OLE DB error 0x80004005 (Client unable to stablish connection) occurred while enumerating packages. A SQL statement issued and failed.
An OLE DB error 0x80004005 (Client unable to stablish connection) occurred while enumerating packages. A SQL statement issued and failed.
There is no service pack installed on the server.
Any help will be greatly appreciated.
Thanks in advance for the help.
Regards.
Hello Frivas,
I have a few questions that I hope will help narrow down your issue.
- Are you running SQL 2005 RTM, SP1 or SP2? I presume 2005 RTM since you said there is no service pack installed on the server, although perhaps you mean Windows service packs?
- When does the error occur? At the end of the wizard, at the end of saving the maintenance plan in the Designer UI? Or somewhere in the process?
- Does the login you're using to connect to the SQL Server have the sysadmin role, or some other roles?
- If the error dialog that comes up includes the small icon for additional details, can you please reproduce the problem and copy and paste the stack trace here?
James
|||..In addition to above I would like to know what is the reason for not having any service packs. You may know that SP2 has all the latest fixes for maintenance plans & ssis issue in this regard. http://download.microsoft.com/download/2/b/5/2b5e5d37-9b17-423d-bc8f-b11ecd4195b4/ReadmeSQL2005SP2.htm fyi.|||I don't understand what is the use of these kind of replys. If you don't know the answer just shut the mouth. Looks like just writing something to increase number of posts.
Everybody working in this field know the importance of installing the service packs.
Error when trying to create a linked server
Hi all,
I have a problem when i try to create a linked server to a MsAccess Db. That's what i do:
linked server drop (in case it already exist)
sp_dropserver 'XXXXX', 'droplogins'
linked server creation
sp_addlinkedserver XXXXX, 'Jet 4.0','Microsoft.Jet.OLEDB.4.0', '\ \server\folder\db1.mdb'
login creation
sp_addlinkedsrvlogin XXXXX, FALSE, NULL, Admin, NULL
fill tables
sp_tables_ex XXXXX
File Db1.mdb is located on a partition (D) of the server where Sql is installed.
On login creation i get the following error :
Error -2147217900 Error during decryption. (15466) Source: Microsoft OLE DB Provider for SQL Server.
(This is not the real error message, it has been translated)
Some ideas?
Thanks
It seems like the system is having problems decrypting the service master key. Have you moved the master DB from one machine to another and/or changed the service service account for SQL server? If you changed the service account, try using the original account.
You can also try the following:
SELECT * FROM sys.dm_os_ring_buffers WHERE ring_buffer_type = 'RING_BUFFER_SECURITY_ERROR'
The information from this DMV will help us find out to determine if indeed it was the SMK decryption or something else.
Thanks,
-Raul Garcia
SDE/T
SQL Server Engine
|||I must verify but i think that the customer has Sql Express 2005 SP1 installed. It's ok for retriving information or he has to install SP2?
Thanks
Peo
|||Unfortunately in order to use the ring buffer DMV you need SQL Server SP2, but that information would only help us to confirm if it was the SMK the one that failed to be decrypted or if it something else. Feel free to update to SP2 if you consider it is necessary
The SMK is protected using DPAPI, and it is linked to the machine and the service account. Hopefully the following questions will help us to find out the root cause of the problem:
· Was the master DB created in a different machine? (i.e. recovered by a RESTORE operation)
· Has the service account for SQL Server service changed?
· What type of account is SQL Server service running as (i.e. domain account, local machine account, local system, network service, etc.)?
Thanks,
-Raul Garcia
SDE/T
SQL Server Engine
Error when trying to create "datasources"
Brand new at this !
I'm running VB 2005 express edition installed from full MS download which included the SQL2005 express server V9.00.1116
Have used the Video tutorial (video 8 & 9) to create a database and have followed instructiions faithfully
Problem.
From the Data / Add New Datasource menu everything proceeds ok - that is a "dataset.xsd" file is created but then I get an error message
" Could not get type information for .........myfilename dataset "
and so the process is not completed properly and a datasource is not created.
I'm unsure what the type information is and have been unsuccesful turning up anything from the help files or forum so hoping someone can maybe tell me whats happening and how to fix this.
Thanks
I also ran into this problem and got it solved by removing the connection strings in 'My Project - Settings'. I hope this also works for you.Harmen.|||
Thanks for that idea
For the record had trouble removing strings however -
My problems have been solved by accident when I created a new windows user account and ran VB express from there. I believe the problem was to do with the connection address because my system name has an " & " in the name(stupid me when I set up Windows XP ) the ampersand maybe an illegal character in a path name.
Here's the full path i used
Data Source=.\SQLEXPRESS;AttachDbFilename="C:\Documents and Settings\TB&MA\My Documents\Visual Studio 2005\Projects\MyDataBase\MyDataBase\Database1.mdf";Integrated Security=True;User Instance=True
I think this why running it from a new user account worked ok as the connection string would have new directory path name
Thanks again
sqlError when trying to create "datasources"
Brand new at this !
I'm running VB 2005 express edition installed from full MS download which included the SQL2005 express server V9.00.1116
Have used the Video tutorial (video 8 & 9) to create a database and have followed instructiions faithfully
Problem.
From the Data / Add New Datasource menu everything proceeds ok - that is a "dataset.xsd" file is created but then I get an error message
" Could not get type information for .........myfilename dataset "
and so the process is not completed properly and a datasource is not created.
I'm unsure what the type information is and have been unsuccesful turning up anything from the help files or forum so hoping someone can maybe tell me whats happening and how to fix this.
Thanks
I also ran into this problem and got it solved by removing the connection strings in 'My Project - Settings'. I hope this also works for you.Harmen.
|||
Thanks for that idea
For the record had trouble removing strings however -
My problems have been solved by accident when I created a new windows user account and ran VB express from there. I believe the problem was to do with the connection address because my system name has an " & " in the name(stupid me when I set up Windows XP ) the ampersand maybe an illegal character in a path name.
Here's the full path i used
Data Source=.\SQLEXPRESS;AttachDbFilename="C:\Documents and Settings\TB&MA\My Documents\Visual Studio 2005\Projects\MyDataBase\MyDataBase\Database1.mdf";Integrated Security=True;User Instance=True
I think this why running it from a new user account worked ok as the connection string would have new directory path name
Thanks again
Monday, March 26, 2012
Error when running a back up job created n a SQL cluster
Hello,
I'm haveing a strange problem. When I run a backup off the database without
making it a schedule job I get a good backup, when I create it as a job and
run it I receive the folowing error:
[SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
01000] (Message 258) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
4035). The step failed.
Can anyone help me out on a solution?
may be anything
but try to check security settings for SQL Agent service account and try to
use only tcp/ip...disable named pipes...
also useful link
http://support.microsoft.com/default...b;en-us;827452
rgds
Sinisa
"robert_at_cbb" wrote:
> Hello,
> I'm haveing a strange problem. When I run a backup off the database without
> making it a schedule job I get a good backup, when I create it as a job and
> run it I receive the folowing error:
> [SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
> 01000] (Message 258) General network error. Check your network
> documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
> 'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
> 4035). The step failed.
> Can anyone help me out on a solution?
I'm haveing a strange problem. When I run a backup off the database without
making it a schedule job I get a good backup, when I create it as a job and
run it I receive the folowing error:
[SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
01000] (Message 258) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
4035). The step failed.
Can anyone help me out on a solution?
may be anything
but try to check security settings for SQL Agent service account and try to
use only tcp/ip...disable named pipes...
also useful link
http://support.microsoft.com/default...b;en-us;827452
rgds
Sinisa
"robert_at_cbb" wrote:
> Hello,
> I'm haveing a strange problem. When I run a backup off the database without
> making it a schedule job I get a good backup, when I create it as a job and
> run it I receive the folowing error:
> [SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
> 01000] (Message 258) General network error. Check your network
> documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
> 'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
> 4035). The step failed.
> Can anyone help me out on a solution?
Error when running a back up job created n a SQL cluster
Hello,
I'm haveing a strange problem. When I run a backup off the database without
making it a schedule job I get a good backup, when I create it as a job and
run it I receive the folowing error:
[SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQ
LSTATE
01000] (Message 258) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for databa
se
'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Erro
r
4035). The step failed.
Can anyone help me out on a solution?may be anything
but try to check security settings for SQL Agent service account and try to
use only tcp/ip...disable named pipes...
also useful link
http://support.microsoft.com/defaul...kb;en-us;827452
rgds
Sinisa
"robert_at_cbb" wrote:
> Hello,
> I'm haveing a strange problem. When I run a backup off the database withou
t
> making it a schedule job I get a good backup, when I create it as a job an
d
> run it I receive the folowing error:
> [SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [
;SQLSTATE
> 01000] (Message 258) General network error. Check your network
> documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for data
base
> 'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Er
ror
> 4035). The step failed.
> Can anyone help me out on a solution?
I'm haveing a strange problem. When I run a backup off the database without
making it a schedule job I get a good backup, when I create it as a job and
run it I receive the folowing error:
[SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQ
LSTATE
01000] (Message 258) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for databa
se
'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Erro
r
4035). The step failed.
Can anyone help me out on a solution?may be anything
but try to check security settings for SQL Agent service account and try to
use only tcp/ip...disable named pipes...
also useful link
http://support.microsoft.com/defaul...kb;en-us;827452
rgds
Sinisa
"robert_at_cbb" wrote:
> Hello,
> I'm haveing a strange problem. When I run a backup off the database withou
t
> making it a schedule job I get a good backup, when I create it as a job an
d
> run it I receive the folowing error:
> [SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [
;SQLSTATE
> 01000] (Message 258) General network error. Check your network
> documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for data
base
> 'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Er
ror
> 4035). The step failed.
> Can anyone help me out on a solution?
Error when running a back up job created n a SQL cluster
Hello,
I'm haveing a strange problem. When I run a backup off the database without
making it a schedule job I get a good backup, when I create it as a job and
run it I receive the folowing error:
[SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
01000] (Message 258) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
4035). The step failed.
Can anyone help me out on a solution?may be anything :)
but try to check security settings for SQL Agent service account and try to
use only tcp/ip...disable named pipes...
also useful link
http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
rgds
Sinisa
"robert_at_cbb" wrote:
> Hello,
> I'm haveing a strange problem. When I run a backup off the database without
> making it a schedule job I get a good backup, when I create it as a job and
> run it I receive the folowing error:
> [SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
> 01000] (Message 258) General network error. Check your network
> documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
> 'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
> 4035). The step failed.
> Can anyone help me out on a solution?
I'm haveing a strange problem. When I run a backup off the database without
making it a schedule job I get a good backup, when I create it as a job and
run it I receive the folowing error:
[SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
01000] (Message 258) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
4035). The step failed.
Can anyone help me out on a solution?may be anything :)
but try to check security settings for SQL Agent service account and try to
use only tcp/ip...disable named pipes...
also useful link
http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
rgds
Sinisa
"robert_at_cbb" wrote:
> Hello,
> I'm haveing a strange problem. When I run a backup off the database without
> making it a schedule job I get a good backup, when I create it as a job and
> run it I receive the folowing error:
> [SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
> 01000] (Message 258) General network error. Check your network
> documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
> 'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
> 4035). The step failed.
> Can anyone help me out on a solution?
Error when restoring the database in SQL
I have 3 database in SQL Server 7.0 (e.g. Company_1, Company_2 and Company_3), and I'm create 2 for new Db (Company_4 and Company_5), when I'm trying to restore from the backup data into the new Db which I just created, there is encounter the error as follow :
"Microsft SQL-DMO (ODBC SQL State : 42000). Backup or restore operation terminating abnormally."
Then the Database has corroupted and not able to open for Db Information.
However, I'm able to do restore in the other Db (the first 3 Db).
Surprise, why there isn't anybody to reply for my problem?, is there anybody to make clarify for my question ?.
|||Do 'restore verifyonly from <backup_device>' to check out the backup file. The message in your post simply means you have a corruption and sqlserver is not able to restore.Monday, March 19, 2012
Error when creating Stored Procedure
I am trying to create a new stored procedure:
****************************************
***************
CREATE PROCEDURE XXX_GetInfo AS
select cast(info.id as varchar) refno, info.begindt, enddt, info.company,
info.type, info.weight
from info info
union
select cast(test.id as varchar) refno, test.begindt, enddt, test.company,
test.type, info.weight
from link1.test.dbo.test test
order by begindt,enddt
****************************************
***************
link1 is a linked server
When I check syntax, sql comes back and says that syntax is correct.
When I try to create the stored procedure, I get an:
[Microsoft SQL-DMO (ODBC SQLState: 42000)]
Error 7405: Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS
options to be set for the connection. This ensures consistent query
semantics. Enable these options and then reissue your query.
I have checked that ANSI_NULLS, ANSI_WARNINGS, and ANSI Padding is
configured as on for both servers.
When Setting up the linked server :
General Tab
Linked server - link1
Other data source - Provider Name - Microsoft OLE DB Provider for
SQL Server
Product name -
Data source - ip address of the server
Provider string -
catalog - test
Security Tab
Be made using this security context - sa of the remote machine
Any help or insight as to why it will not allow me to create the stored
procedure will be greatly appreciated.
Thanks in Advance
VinceServer settings are overridden by tool settings which are overriden by
explicit SET settings. So just issue the appropriate SET statements in the
same query window where you are executing the create proc statement.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Vince,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with this
issue.
I think Cindy has pointed out the root cause that the server settings are ov
eridden. To explicit
that settings in either Enterprise Manager or Query Analyzer, you should iss
ue the SET within
the CREATE PROCEDURE so that these setting will not be affected by SQL state
ments in
anohter Client Tools . Otherwise, the life span of these settings ends with
the batch finishes
and they may be OFF before you create your procedure.
Please look through the following script and see if it works on your side. I
f there is anything
more we can do to assist you, please feel free to post it in the group.
---
CREATE PROCEDURE XXX_GetInfo
AS
SET ANSI_NULLS ON
SET ANSI_WARNINGS ON
GO
select cast(info.id as varchar) refno, info.begindt, enddt, info.company,
info.type, info.weight
from info info
union
select cast(test.id as varchar) refno, test.begindt, enddt, test.company,
test.type, info.weight
from link1.test.dbo.test test
order by begindt,enddt
GO
---
Best regards,
Billy Yao
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
****************************************
***************
CREATE PROCEDURE XXX_GetInfo AS
select cast(info.id as varchar) refno, info.begindt, enddt, info.company,
info.type, info.weight
from info info
union
select cast(test.id as varchar) refno, test.begindt, enddt, test.company,
test.type, info.weight
from link1.test.dbo.test test
order by begindt,enddt
****************************************
***************
link1 is a linked server
When I check syntax, sql comes back and says that syntax is correct.
When I try to create the stored procedure, I get an:
[Microsoft SQL-DMO (ODBC SQLState: 42000)]
Error 7405: Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS
options to be set for the connection. This ensures consistent query
semantics. Enable these options and then reissue your query.
I have checked that ANSI_NULLS, ANSI_WARNINGS, and ANSI Padding is
configured as on for both servers.
When Setting up the linked server :
General Tab
Linked server - link1
Other data source - Provider Name - Microsoft OLE DB Provider for
SQL Server
Product name -
Data source - ip address of the server
Provider string -
catalog - test
Security Tab
Be made using this security context - sa of the remote machine
Any help or insight as to why it will not allow me to create the stored
procedure will be greatly appreciated.
Thanks in Advance
VinceServer settings are overridden by tool settings which are overriden by
explicit SET settings. So just issue the appropriate SET statements in the
same query window where you are executing the create proc statement.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Vince,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with this
issue.
I think Cindy has pointed out the root cause that the server settings are ov
eridden. To explicit
that settings in either Enterprise Manager or Query Analyzer, you should iss
ue the SET within
the CREATE PROCEDURE so that these setting will not be affected by SQL state
ments in
anohter Client Tools . Otherwise, the life span of these settings ends with
the batch finishes
and they may be OFF before you create your procedure.
Please look through the following script and see if it works on your side. I
f there is anything
more we can do to assist you, please feel free to post it in the group.
---
CREATE PROCEDURE XXX_GetInfo
AS
SET ANSI_NULLS ON
SET ANSI_WARNINGS ON
GO
select cast(info.id as varchar) refno, info.begindt, enddt, info.company,
info.type, info.weight
from info info
union
select cast(test.id as varchar) refno, test.begindt, enddt, test.company,
test.type, info.weight
from link1.test.dbo.test test
order by begindt,enddt
GO
---
Best regards,
Billy Yao
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
Error when creating new database user
When I try to create a new database user (on any database) I get this error
message: Cannot resolve
collation conflict for equal to operation.
I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
database has another collation: Danish_Norwegian_CI_AI and the tempdb
database. I don't know why the tempdb has this collation, and if that is the
problem?
I'd start checking the collation for below databases:
master
model
tempdb
msdb
If they aren't the same, you have a problem. It isn't supported to have different collations for the
system databases. Somebody made a "hack" to get you there. You would need to sort it out. Suitable
actions depend on what collation each system database has.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
> When I try to create a new database user (on any database) I get this error
> message: Cannot resolve
> collation conflict for equal to operation.
> I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
> database has another collation: Danish_Norwegian_CI_AI and the tempdb
> database. I don't know why the tempdb has this collation, and if that is the
> problem?
|||The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
It is not possible to change collation in tempdb with alter
database...because it is a system database. What can I do?
"Tibor Karaszi" wrote:
> I'd start checking the collation for below databases:
> master
> model
> tempdb
> msdb
> If they aren't the same, you have a problem. It isn't supported to have different collations for the
> system databases. Somebody made a "hack" to get you there. You would need to sort it out. Suitable
> actions depend on what collation each system database has.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
>
|||Probably somebody moved files for the model database from another installation. Tempdb is created
based on model on each startup. Hunt down database files from an installation that matches system
and msdb for your model database. You can try to just stop SQL Server and replace the files (backup
first, and save a copy of original model database files).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...[vbcol=seagreen]
> The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
|||Also, you could try bringing up the instance in master recovery only and
then attempt to modify the collation using the ALTER DATABASE command.
-T3608
ALTER DATABASE model
COLLATE <collation name>
This may only be a pseudo fix, if it works at all. You will probably need
to do as Tibor suggest, but it is worth a shot if you have trouble finding
such a database.
Another way to acquire a model database with the collation you want would be
to install SQL Server Developer Edition on your workstation and specifying
the collation of the system databases during the installation. You would
then need to patch you workstation installation to the same level as your
production database before you tried to copy the files from your workstation
to the server.
Hope this helps.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239R%23RH3ZFHA.1040@.TK2MSFTNGP10.phx.gbl...
Probably somebody moved files for the model database from another
installation. Tempdb is created
based on model on each startup. Hunt down database files from an
installation that matches system
and msdb for your model database. You can try to just stop SQL Server and
replace the files (backup
first, and save a copy of original model database files).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...
> The master and msdb is ok, but tempdb and model have
Danish_Norwegian_CI_AI[vbcol=seagreen]
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
different collations for[vbcol=seagreen]
to sort it out.[vbcol=seagreen]
error[vbcol=seagreen]
is the[vbcol=seagreen]
message: Cannot resolve
collation conflict for equal to operation.
I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
database has another collation: Danish_Norwegian_CI_AI and the tempdb
database. I don't know why the tempdb has this collation, and if that is the
problem?
I'd start checking the collation for below databases:
master
model
tempdb
msdb
If they aren't the same, you have a problem. It isn't supported to have different collations for the
system databases. Somebody made a "hack" to get you there. You would need to sort it out. Suitable
actions depend on what collation each system database has.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
> When I try to create a new database user (on any database) I get this error
> message: Cannot resolve
> collation conflict for equal to operation.
> I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
> database has another collation: Danish_Norwegian_CI_AI and the tempdb
> database. I don't know why the tempdb has this collation, and if that is the
> problem?
|||The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
It is not possible to change collation in tempdb with alter
database...because it is a system database. What can I do?
"Tibor Karaszi" wrote:
> I'd start checking the collation for below databases:
> master
> model
> tempdb
> msdb
> If they aren't the same, you have a problem. It isn't supported to have different collations for the
> system databases. Somebody made a "hack" to get you there. You would need to sort it out. Suitable
> actions depend on what collation each system database has.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
>
|||Probably somebody moved files for the model database from another installation. Tempdb is created
based on model on each startup. Hunt down database files from an installation that matches system
and msdb for your model database. You can try to just stop SQL Server and replace the files (backup
first, and save a copy of original model database files).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...[vbcol=seagreen]
> The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
|||Also, you could try bringing up the instance in master recovery only and
then attempt to modify the collation using the ALTER DATABASE command.
-T3608
ALTER DATABASE model
COLLATE <collation name>
This may only be a pseudo fix, if it works at all. You will probably need
to do as Tibor suggest, but it is worth a shot if you have trouble finding
such a database.
Another way to acquire a model database with the collation you want would be
to install SQL Server Developer Edition on your workstation and specifying
the collation of the system databases during the installation. You would
then need to patch you workstation installation to the same level as your
production database before you tried to copy the files from your workstation
to the server.
Hope this helps.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239R%23RH3ZFHA.1040@.TK2MSFTNGP10.phx.gbl...
Probably somebody moved files for the model database from another
installation. Tempdb is created
based on model on each startup. Hunt down database files from an
installation that matches system
and msdb for your model database. You can try to just stop SQL Server and
replace the files (backup
first, and save a copy of original model database files).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...
> The master and msdb is ok, but tempdb and model have
Danish_Norwegian_CI_AI[vbcol=seagreen]
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
different collations for[vbcol=seagreen]
to sort it out.[vbcol=seagreen]
error[vbcol=seagreen]
is the[vbcol=seagreen]
Error when creating new database user
When I try to create a new database user (on any database) I get this error
message: Cannot resolve
collation conflict for equal to operation.
I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
database has another collation: Danish_Norwegian_CI_AI and the tempdb
database. I don't know why the tempdb has this collation, and if that is the
problem?I'd start checking the collation for below databases:
master
model
tempdb
msdb
If they aren't the same, you have a problem. It isn't supported to have diff
erent collations for the
system databases. Somebody made a "hack" to get you there. You would need to
sort it out. Suitable
actions depend on what collation each system database has.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
> When I try to create a new database user (on any database) I get this erro
r
> message: Cannot resolve
> collation conflict for equal to operation.
> I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
> database has another collation: Danish_Norwegian_CI_AI and the tempdb
> database. I don't know why the tempdb has this collation, and if that is t
he
> problem?|||The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
It is not possible to change collation in tempdb with alter
database...because it is a system database. What can I do?
"Tibor Karaszi" wrote:
> I'd start checking the collation for below databases:
> master
> model
> tempdb
> msdb
> If they aren't the same, you have a problem. It isn't supported to have di
fferent collations for the
> system databases. Somebody made a "hack" to get you there. You would need
to sort it out. Suitable
> actions depend on what collation each system database has.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
>|||Probably somebody moved files for the model database from another installati
on. Tempdb is created
based on model on each startup. Hunt down database files from an installatio
n that matches system
and msdb for your model database. You can try to just stop SQL Server and re
place the files (backup
first, and save a copy of original model database files).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...[vbcol=seagreen]
> The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_A
I
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
>|||Also, you could try bringing up the instance in master recovery only and
then attempt to modify the collation using the ALTER DATABASE command.
-T3608
ALTER DATABASE model
COLLATE <collation name>
This may only be a pseudo fix, if it works at all. You will probably need
to do as Tibor suggest, but it is worth a shot if you have trouble finding
such a database.
Another way to acquire a model database with the collation you want would be
to install SQL Server Developer Edition on your workstation and specifying
the collation of the system databases during the installation. You would
then need to patch you workstation installation to the same level as your
production database before you tried to copy the files from your workstation
to the server.
Hope this helps.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239R%23RH3ZFHA.1040@.TK2MSFTNGP10.phx.gbl...
Probably somebody moved files for the model database from another
installation. Tempdb is created
based on model on each startup. Hunt down database files from an
installation that matches system
and msdb for your model database. You can try to just stop SQL Server and
replace the files (backup
first, and save a copy of original model database files).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...
> The master and msdb is ok, but tempdb and model have
Danish_Norwegian_CI_AI[vbcol=seagreen]
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
>
different collations for[vbcol=seagreen]
to sort it out.[vbcol=seagreen]
error[vbcol=seagreen]
is the[vbcol=seagreen]
message: Cannot resolve
collation conflict for equal to operation.
I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
database has another collation: Danish_Norwegian_CI_AI and the tempdb
database. I don't know why the tempdb has this collation, and if that is the
problem?I'd start checking the collation for below databases:
master
model
tempdb
msdb
If they aren't the same, you have a problem. It isn't supported to have diff
erent collations for the
system databases. Somebody made a "hack" to get you there. You would need to
sort it out. Suitable
actions depend on what collation each system database has.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
> When I try to create a new database user (on any database) I get this erro
r
> message: Cannot resolve
> collation conflict for equal to operation.
> I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
> database has another collation: Danish_Norwegian_CI_AI and the tempdb
> database. I don't know why the tempdb has this collation, and if that is t
he
> problem?|||The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
It is not possible to change collation in tempdb with alter
database...because it is a system database. What can I do?
"Tibor Karaszi" wrote:
> I'd start checking the collation for below databases:
> master
> model
> tempdb
> msdb
> If they aren't the same, you have a problem. It isn't supported to have di
fferent collations for the
> system databases. Somebody made a "hack" to get you there. You would need
to sort it out. Suitable
> actions depend on what collation each system database has.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
>|||Probably somebody moved files for the model database from another installati
on. Tempdb is created
based on model on each startup. Hunt down database files from an installatio
n that matches system
and msdb for your model database. You can try to just stop SQL Server and re
place the files (backup
first, and save a copy of original model database files).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...[vbcol=seagreen]
> The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_A
I
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
>|||Also, you could try bringing up the instance in master recovery only and
then attempt to modify the collation using the ALTER DATABASE command.
-T3608
ALTER DATABASE model
COLLATE <collation name>
This may only be a pseudo fix, if it works at all. You will probably need
to do as Tibor suggest, but it is worth a shot if you have trouble finding
such a database.
Another way to acquire a model database with the collation you want would be
to install SQL Server Developer Edition on your workstation and specifying
the collation of the system databases during the installation. You would
then need to patch you workstation installation to the same level as your
production database before you tried to copy the files from your workstation
to the server.
Hope this helps.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239R%23RH3ZFHA.1040@.TK2MSFTNGP10.phx.gbl...
Probably somebody moved files for the model database from another
installation. Tempdb is created
based on model on each startup. Hunt down database files from an
installation that matches system
and msdb for your model database. You can try to just stop SQL Server and
replace the files (backup
first, and save a copy of original model database files).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...
> The master and msdb is ok, but tempdb and model have
Danish_Norwegian_CI_AI[vbcol=seagreen]
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
>
different collations for[vbcol=seagreen]
to sort it out.[vbcol=seagreen]
error[vbcol=seagreen]
is the[vbcol=seagreen]
Error when creating new database user
When I try to create a new database user (on any database) I get this error
message: Cannot resolve
collation conflict for equal to operation.
I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
database has another collation: Danish_Norwegian_CI_AI and the tempdb
database. I don't know why the tempdb has this collation, and if that is the
problem?I'd start checking the collation for below databases:
master
model
tempdb
msdb
If they aren't the same, you have a problem. It isn't supported to have different collations for the
system databases. Somebody made a "hack" to get you there. You would need to sort it out. Suitable
actions depend on what collation each system database has.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
> When I try to create a new database user (on any database) I get this error
> message: Cannot resolve
> collation conflict for equal to operation.
> I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
> database has another collation: Danish_Norwegian_CI_AI and the tempdb
> database. I don't know why the tempdb has this collation, and if that is the
> problem?|||The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
It is not possible to change collation in tempdb with alter
database...because it is a system database. What can I do?
"Tibor Karaszi" wrote:
> I'd start checking the collation for below databases:
> master
> model
> tempdb
> msdb
> If they aren't the same, you have a problem. It isn't supported to have different collations for the
> system databases. Somebody made a "hack" to get you there. You would need to sort it out. Suitable
> actions depend on what collation each system database has.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
> > When I try to create a new database user (on any database) I get this error
> > message: Cannot resolve
> > collation conflict for equal to operation.
> > I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
> > database has another collation: Danish_Norwegian_CI_AI and the tempdb
> > database. I don't know why the tempdb has this collation, and if that is the
> > problem?
>|||Probably somebody moved files for the model database from another installation. Tempdb is created
based on model on each startup. Hunt down database files from an installation that matches system
and msdb for your model database. You can try to just stop SQL Server and replace the files (backup
first, and save a copy of original model database files).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...
> The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
>> I'd start checking the collation for below databases:
>> master
>> model
>> tempdb
>> msdb
>> If they aren't the same, you have a problem. It isn't supported to have different collations for
>> the
>> system databases. Somebody made a "hack" to get you there. You would need to sort it out.
>> Suitable
>> actions depend on what collation each system database has.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
>> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
>> > When I try to create a new database user (on any database) I get this error
>> > message: Cannot resolve
>> > collation conflict for equal to operation.
>> > I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
>> > database has another collation: Danish_Norwegian_CI_AI and the tempdb
>> > database. I don't know why the tempdb has this collation, and if that is the
>> > problem?
>>|||Also, you could try bringing up the instance in master recovery only and
then attempt to modify the collation using the ALTER DATABASE command.
-T3608
ALTER DATABASE model
COLLATE <collation name>
This may only be a pseudo fix, if it works at all. You will probably need
to do as Tibor suggest, but it is worth a shot if you have trouble finding
such a database.
Another way to acquire a model database with the collation you want would be
to install SQL Server Developer Edition on your workstation and specifying
the collation of the system databases during the installation. You would
then need to patch you workstation installation to the same level as your
production database before you tried to copy the files from your workstation
to the server.
Hope this helps.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239R%23RH3ZFHA.1040@.TK2MSFTNGP10.phx.gbl...
Probably somebody moved files for the model database from another
installation. Tempdb is created
based on model on each startup. Hunt down database files from an
installation that matches system
and msdb for your model database. You can try to just stop SQL Server and
replace the files (backup
first, and save a copy of original model database files).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...
> The master and msdb is ok, but tempdb and model have
Danish_Norwegian_CI_AI
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
>> I'd start checking the collation for below databases:
>> master
>> model
>> tempdb
>> msdb
>> If they aren't the same, you have a problem. It isn't supported to have
different collations for
>> the
>> system databases. Somebody made a "hack" to get you there. You would need
to sort it out.
>> Suitable
>> actions depend on what collation each system database has.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
>> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
>> > When I try to create a new database user (on any database) I get this
error
>> > message: Cannot resolve
>> > collation conflict for equal to operation.
>> > I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
>> > database has another collation: Danish_Norwegian_CI_AI and the tempdb
>> > database. I don't know why the tempdb has this collation, and if that
is the
>> > problem?
>>
message: Cannot resolve
collation conflict for equal to operation.
I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
database has another collation: Danish_Norwegian_CI_AI and the tempdb
database. I don't know why the tempdb has this collation, and if that is the
problem?I'd start checking the collation for below databases:
master
model
tempdb
msdb
If they aren't the same, you have a problem. It isn't supported to have different collations for the
system databases. Somebody made a "hack" to get you there. You would need to sort it out. Suitable
actions depend on what collation each system database has.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
> When I try to create a new database user (on any database) I get this error
> message: Cannot resolve
> collation conflict for equal to operation.
> I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
> database has another collation: Danish_Norwegian_CI_AI and the tempdb
> database. I don't know why the tempdb has this collation, and if that is the
> problem?|||The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
It is not possible to change collation in tempdb with alter
database...because it is a system database. What can I do?
"Tibor Karaszi" wrote:
> I'd start checking the collation for below databases:
> master
> model
> tempdb
> msdb
> If they aren't the same, you have a problem. It isn't supported to have different collations for the
> system databases. Somebody made a "hack" to get you there. You would need to sort it out. Suitable
> actions depend on what collation each system database has.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
> > When I try to create a new database user (on any database) I get this error
> > message: Cannot resolve
> > collation conflict for equal to operation.
> > I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
> > database has another collation: Danish_Norwegian_CI_AI and the tempdb
> > database. I don't know why the tempdb has this collation, and if that is the
> > problem?
>|||Probably somebody moved files for the model database from another installation. Tempdb is created
based on model on each startup. Hunt down database files from an installation that matches system
and msdb for your model database. You can try to just stop SQL Server and replace the files (backup
first, and save a copy of original model database files).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...
> The master and msdb is ok, but tempdb and model have Danish_Norwegian_CI_AI
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
>> I'd start checking the collation for below databases:
>> master
>> model
>> tempdb
>> msdb
>> If they aren't the same, you have a problem. It isn't supported to have different collations for
>> the
>> system databases. Somebody made a "hack" to get you there. You would need to sort it out.
>> Suitable
>> actions depend on what collation each system database has.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
>> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
>> > When I try to create a new database user (on any database) I get this error
>> > message: Cannot resolve
>> > collation conflict for equal to operation.
>> > I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
>> > database has another collation: Danish_Norwegian_CI_AI and the tempdb
>> > database. I don't know why the tempdb has this collation, and if that is the
>> > problem?
>>|||Also, you could try bringing up the instance in master recovery only and
then attempt to modify the collation using the ALTER DATABASE command.
-T3608
ALTER DATABASE model
COLLATE <collation name>
This may only be a pseudo fix, if it works at all. You will probably need
to do as Tibor suggest, but it is worth a shot if you have trouble finding
such a database.
Another way to acquire a model database with the collation you want would be
to install SQL Server Developer Edition on your workstation and specifying
the collation of the system databases during the installation. You would
then need to patch you workstation installation to the same level as your
production database before you tried to copy the files from your workstation
to the server.
Hope this helps.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239R%23RH3ZFHA.1040@.TK2MSFTNGP10.phx.gbl...
Probably somebody moved files for the model database from another
installation. Tempdb is created
based on model on each startup. Hunt down database files from an
installation that matches system
and msdb for your model database. You can try to just stop SQL Server and
replace the files (backup
first, and save a copy of original model database files).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"blaairis" <blaairis@.discussions.microsoft.com> wrote in message
news:2155EF0D-3115-4B69-854B-1DD0C7A02EDC@.microsoft.com...
> The master and msdb is ok, but tempdb and model have
Danish_Norwegian_CI_AI
> It is not possible to change collation in tempdb with alter
> database...because it is a system database. What can I do?
> "Tibor Karaszi" wrote:
>> I'd start checking the collation for below databases:
>> master
>> model
>> tempdb
>> msdb
>> If they aren't the same, you have a problem. It isn't supported to have
different collations for
>> the
>> system databases. Somebody made a "hack" to get you there. You would need
to sort it out.
>> Suitable
>> actions depend on what collation each system database has.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "blaairis" <blaairis@.discussions.microsoft.com> wrote in message
>> news:EC58D0F5-4199-4353-8576-81B6F6BAF41F@.microsoft.com...
>> > When I try to create a new database user (on any database) I get this
error
>> > message: Cannot resolve
>> > collation conflict for equal to operation.
>> > I Use SQL_Danish_Pref_CP1_CI_AS as the default collation. Only one user
>> > database has another collation: Danish_Norwegian_CI_AI and the tempdb
>> > database. I don't know why the tempdb has this collation, and if that
is the
>> > problem?
>>
Error when creating new connection in DTS Designer
64b SQL2005 EE and all clent tools installed on the same server. Im trying to create a new connection in DTS Designer but after succesful test of the connection it errors out with
The new connection manager couldnt be created. Additional info : Exeption from HRESULT 0xC0010014
Any idea whats the problem here?
This might be caused by a problem described here:
http://support.microsoft.com/kb/913817
|||Im logged in with local admin account. Does that count? Still SSIS is running under Network Servise|||Usually the service does the component enumeration and caches the results, so this is performed without admin rights. You can check if this is an issue by temporary disabling the service, and trying this again (restart BIDS first). If this is caused by permission issue, you'll likely succeed because BIDS will do the component enumeration itself (this harms performance, but avoids Network Service restrictions).Error when creating a table based function
I'm trying to create a table based function using SMO. The problem is that I get an error saying that I need to set the DataType property on the function before it can be created. However, the documentation clearly says that the DataType property is null for Table based functions. I can't even set this value to null either!
Here's a code snippet that shows what I'm trying to do.
if (returnType.ToLower() != "table")
{
Type clrDataType = Type.GetType(returnType);
returnSqlDataType = GetSqlDataType(clrDataType);
function.FunctionType = Smo.UserDefinedFunctionType.Scalar;
function.DataType = returnSqlDataType;
}
else
{
function.FunctionType = Smo.UserDefinedFunctionType.Table;
function.TableVariableName = xmlNode.Attributes["tableVariableName"].Value;
XmlNode returnTableDescription = GetChildOfParent(xmlNode, "ReturnTableDescription");
XmlNode columnsNode = GetChildOfParent(returnTableDescription, "Columns");
foreach (XmlNode columnNode in columnsNode.ChildNodes)
{
function.Columns.Add(CreateUdfColumn(function, columnNode));
}
}
The xmlNode that is being referenced is an XmlNode that is describing how to create the table. returnType is a variable that is set from one of the xmlNode's attributes.
When I call on function.Create() then I get the error that I posted above. Any help anyone can give is appreciated. One thing I also tried doing was to connect to an already existing Table based function and look at its SMO properties. Sure enough, its DataType property was null.
MSFT: Is this a bug?
Never mind on this post.....it was my mistake. The DataType property not being set wasn't on the function itself, but rather on the columns collection.
Problem solved.
Error when creating a maintenance plan
When using the maintenance plan wizard on SQL 2005 (RTM) when pressing
the finish button the following error occurs when trying to create the
plan.
Maintenance Plan Wizard Progress
Create maintenance plan failed.
Additional Information:
Create failed for JobStep 'Subplan'.
(Microsoft.SqlServer.MaintenancePlanTasks)
An Exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum-sqlagent_subsystems). (Microsoft SQL Server, Error 14234)
The job appears in the Job Activity Monitor but greyed out and the
maintenance plan is not listed in its section.
What has caused this issue and how can I resolve it?
You need to apply at least SP1 to your SQL Server instance to make
Maintanence Plan work properly. It'd be better if you apply SP2, it contains
lots of fixes.
Ekrem nsoy
"Robin9876" <robin9876@.hotmail.com> wrote in message
news:9c65cf4b-d7b1-4224-bc11-46da57c143c3@.i12g2000prf.googlegroups.com...
> When using the maintenance plan wizard on SQL 2005 (RTM) when pressing
> the finish button the following error occurs when trying to create the
> plan.
> Maintenance Plan Wizard Progress
> Create maintenance plan failed.
> Additional Information:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> An Exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum-sqlagent_subsystems). (Microsoft SQL Server, Error 14234)
>
> The job appears in the Job Activity Monitor but greyed out and the
> maintenance plan is not listed in its section.
> What has caused this issue and how can I resolve it?
|||Addition: If you do not install SSIS you'll not be able to use Maintanence
Plans in RTM version of SQL Server 2005. It's possible to use Maintanence
Plans without SSIS if you apply SP2.
Ekrem nsoy
"Robin9876" <robin9876@.hotmail.com> wrote in message
news:9c65cf4b-d7b1-4224-bc11-46da57c143c3@.i12g2000prf.googlegroups.com...
> When using the maintenance plan wizard on SQL 2005 (RTM) when pressing
> the finish button the following error occurs when trying to create the
> plan.
> Maintenance Plan Wizard Progress
> Create maintenance plan failed.
> Additional Information:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> An Exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum-sqlagent_subsystems). (Microsoft SQL Server, Error 14234)
>
> The job appears in the Job Activity Monitor but greyed out and the
> maintenance plan is not listed in its section.
> What has caused this issue and how can I resolve it?
the finish button the following error occurs when trying to create the
plan.
Maintenance Plan Wizard Progress
Create maintenance plan failed.
Additional Information:
Create failed for JobStep 'Subplan'.
(Microsoft.SqlServer.MaintenancePlanTasks)
An Exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum-sqlagent_subsystems). (Microsoft SQL Server, Error 14234)
The job appears in the Job Activity Monitor but greyed out and the
maintenance plan is not listed in its section.
What has caused this issue and how can I resolve it?
You need to apply at least SP1 to your SQL Server instance to make
Maintanence Plan work properly. It'd be better if you apply SP2, it contains
lots of fixes.
Ekrem nsoy
"Robin9876" <robin9876@.hotmail.com> wrote in message
news:9c65cf4b-d7b1-4224-bc11-46da57c143c3@.i12g2000prf.googlegroups.com...
> When using the maintenance plan wizard on SQL 2005 (RTM) when pressing
> the finish button the following error occurs when trying to create the
> plan.
> Maintenance Plan Wizard Progress
> Create maintenance plan failed.
> Additional Information:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> An Exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum-sqlagent_subsystems). (Microsoft SQL Server, Error 14234)
>
> The job appears in the Job Activity Monitor but greyed out and the
> maintenance plan is not listed in its section.
> What has caused this issue and how can I resolve it?
|||Addition: If you do not install SSIS you'll not be able to use Maintanence
Plans in RTM version of SQL Server 2005. It's possible to use Maintanence
Plans without SSIS if you apply SP2.
Ekrem nsoy
"Robin9876" <robin9876@.hotmail.com> wrote in message
news:9c65cf4b-d7b1-4224-bc11-46da57c143c3@.i12g2000prf.googlegroups.com...
> When using the maintenance plan wizard on SQL 2005 (RTM) when pressing
> the finish button the following error occurs when trying to create the
> plan.
> Maintenance Plan Wizard Progress
> Create maintenance plan failed.
> Additional Information:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> An Exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum-sqlagent_subsystems). (Microsoft SQL Server, Error 14234)
>
> The job appears in the Job Activity Monitor but greyed out and the
> maintenance plan is not listed in its section.
> What has caused this issue and how can I resolve it?
Error when creating a maintenance plan
When using the maintenance plan wizard on SQL 2005 (RTM) when pressing
the finish button the following error occurs when trying to create the
plan.
Maintenance Plan Wizard Progress
Create maintenance plan failed.
Additional Information:
Create failed for JobStep 'Subplan'.
(Microsoft.SqlServer.MaintenancePlanTasks)
An Exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum-sqlagent_subsystems). (Microsoft SQL Server, Error 14234)
The job appears in the Job Activity Monitor but greyed out and the
maintenance plan is not listed in its section.
What has caused this issue and how can I resolve it?You need to apply at least SP1 to your SQL Server instance to make
Maintanence Plan work properly. It'd be better if you apply SP2, it contains
lots of fixes.
Ekrem nsoy
"Robin9876" <robin9876@.hotmail.com> wrote in message
news:9c65cf4b-d7b1-4224-bc11-46da57c143c3@.i12g2000prf.googlegroups.com...
> When using the maintenance plan wizard on SQL 2005 (RTM) when pressing
> the finish button the following error occurs when trying to create the
> plan.
> Maintenance Plan Wizard Progress
> Create maintenance plan failed.
> Additional Information:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> An Exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum-sqlagent_subsystems). (Microsoft SQL Server, Error 14234)
>
> The job appears in the Job Activity Monitor but greyed out and the
> maintenance plan is not listed in its section.
> What has caused this issue and how can I resolve it?|||Addition: If you do not install SSIS you'll not be able to use Maintanence
Plans in RTM version of SQL Server 2005. It's possible to use Maintanence
Plans without SSIS if you apply SP2.
Ekrem nsoy
"Robin9876" <robin9876@.hotmail.com> wrote in message
news:9c65cf4b-d7b1-4224-bc11-46da57c143c3@.i12g2000prf.googlegroups.com...
> When using the maintenance plan wizard on SQL 2005 (RTM) when pressing
> the finish button the following error occurs when trying to create the
> plan.
> Maintenance Plan Wizard Progress
> Create maintenance plan failed.
> Additional Information:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> An Exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum-sqlagent_subsystems). (Microsoft SQL Server, Error 14234)
>
> The job appears in the Job Activity Monitor but greyed out and the
> maintenance plan is not listed in its section.
> What has caused this issue and how can I resolve it?
the finish button the following error occurs when trying to create the
plan.
Maintenance Plan Wizard Progress
Create maintenance plan failed.
Additional Information:
Create failed for JobStep 'Subplan'.
(Microsoft.SqlServer.MaintenancePlanTasks)
An Exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum-sqlagent_subsystems). (Microsoft SQL Server, Error 14234)
The job appears in the Job Activity Monitor but greyed out and the
maintenance plan is not listed in its section.
What has caused this issue and how can I resolve it?You need to apply at least SP1 to your SQL Server instance to make
Maintanence Plan work properly. It'd be better if you apply SP2, it contains
lots of fixes.
Ekrem nsoy
"Robin9876" <robin9876@.hotmail.com> wrote in message
news:9c65cf4b-d7b1-4224-bc11-46da57c143c3@.i12g2000prf.googlegroups.com...
> When using the maintenance plan wizard on SQL 2005 (RTM) when pressing
> the finish button the following error occurs when trying to create the
> plan.
> Maintenance Plan Wizard Progress
> Create maintenance plan failed.
> Additional Information:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> An Exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum-sqlagent_subsystems). (Microsoft SQL Server, Error 14234)
>
> The job appears in the Job Activity Monitor but greyed out and the
> maintenance plan is not listed in its section.
> What has caused this issue and how can I resolve it?|||Addition: If you do not install SSIS you'll not be able to use Maintanence
Plans in RTM version of SQL Server 2005. It's possible to use Maintanence
Plans without SSIS if you apply SP2.
Ekrem nsoy
"Robin9876" <robin9876@.hotmail.com> wrote in message
news:9c65cf4b-d7b1-4224-bc11-46da57c143c3@.i12g2000prf.googlegroups.com...
> When using the maintenance plan wizard on SQL 2005 (RTM) when pressing
> the finish button the following error occurs when trying to create the
> plan.
> Maintenance Plan Wizard Progress
> Create maintenance plan failed.
> Additional Information:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> An Exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum-sqlagent_subsystems). (Microsoft SQL Server, Error 14234)
>
> The job appears in the Job Activity Monitor but greyed out and the
> maintenance plan is not listed in its section.
> What has caused this issue and how can I resolve it?
Subscribe to:
Posts (Atom)