Wednesday, March 21, 2012
Migrate from user instance to native db in SQL Server Express ?
I am currently looking at migrating a database which has been running in
"user instance" mode, onto the standard sql server express mode. Basically I
need to be able to connect to the database while it's running from other
scripts and the management studio, which I cannot do nicely while the DB is
running in user mode.
Is there any tools or good instructions on doing this?
At this point I've re-created the database from scratch and imported data,
however I am looking for a cleaner/effective way of doing this. Any
suggestions?Hi
I am not a SQLExpress expert, ut SSEUTIL will allow you to attach to a user
instance of SQL Express.
http://www.microsoft.com/downloads/...&DisplayLang=en
You could then detach (sp_detach_db) the database and re-attach
(sp_attach_db) it to the main instance of SQL Server.
You would need to change the connection string in the application that
creates the user instance to reference the main instance of SQL Server and
not create the user instance.
John
"NSiggel" wrote:
> Hello,
> I am currently looking at migrating a database which has been running in
> "user instance" mode, onto the standard sql server express mode. Basically
I
> need to be able to connect to the database while it's running from other
> scripts and the management studio, which I cannot do nicely while the DB i
s
> running in user mode.
> Is there any tools or good instructions on doing this?
> At this point I've re-created the database from scratch and imported data,
> however I am looking for a cleaner/effective way of doing this. Any
> suggestions?
>sql
Migrate from user instance to native db in SQL Server Express ?
I am currently looking at migrating a database which has been running in
"user instance" mode, onto the standard sql server express mode. Basically I
need to be able to connect to the database while it's running from other
scripts and the management studio, which I cannot do nicely while the DB is
running in user mode.
Is there any tools or good instructions on doing this?
At this point I've re-created the database from scratch and imported data,
however I am looking for a cleaner/effective way of doing this. Any
suggestions?
Hi
I am not a SQLExpress expert, ut SSEUTIL will allow you to attach to a user
instance of SQL Express.
http://www.microsoft.com/downloads/details.aspx?FamilyID=fa87e828-173f-472e-a85c-27ed01cf6b02&DisplayLang=en
You could then detach (sp_detach_db) the database and re-attach
(sp_attach_db) it to the main instance of SQL Server.
You would need to change the connection string in the application that
creates the user instance to reference the main instance of SQL Server and
not create the user instance.
John
"NSiggel" wrote:
> Hello,
> I am currently looking at migrating a database which has been running in
> "user instance" mode, onto the standard sql server express mode. Basically I
> need to be able to connect to the database while it's running from other
> scripts and the management studio, which I cannot do nicely while the DB is
> running in user mode.
> Is there any tools or good instructions on doing this?
> At this point I've re-created the database from scratch and imported data,
> however I am looking for a cleaner/effective way of doing this. Any
> suggestions?
>
Migrate from user instance to native db in SQL Server Express ?
I am currently looking at migrating a database which has been running in
"user instance" mode, onto the standard sql server express mode. Basically I
need to be able to connect to the database while it's running from other
scripts and the management studio, which I cannot do nicely while the DB is
running in user mode.
Is there any tools or good instructions on doing this?
At this point I've re-created the database from scratch and imported data,
however I am looking for a cleaner/effective way of doing this. Any
suggestions?Hi
I am not a SQLExpress expert, ut SSEUTIL will allow you to attach to a user
instance of SQL Express.
http://www.microsoft.com/downloads/details.aspx?FamilyID=fa87e828-173f-472e-a85c-27ed01cf6b02&DisplayLang=en
You could then detach (sp_detach_db) the database and re-attach
(sp_attach_db) it to the main instance of SQL Server.
You would need to change the connection string in the application that
creates the user instance to reference the main instance of SQL Server and
not create the user instance.
John
"NSiggel" wrote:
> Hello,
> I am currently looking at migrating a database which has been running in
> "user instance" mode, onto the standard sql server express mode. Basically I
> need to be able to connect to the database while it's running from other
> scripts and the management studio, which I cannot do nicely while the DB is
> running in user mode.
> Is there any tools or good instructions on doing this?
> At this point I've re-created the database from scratch and imported data,
> however I am looking for a cleaner/effective way of doing this. Any
> suggestions?
>
Friday, February 24, 2012
Microsoft SQL Server, Error: 10053
O get this error when trying to connect to my database. About 5 minutes ago it was working fine...seems to go in and out. We have native client installed in this server as well so not sure why I keep having connection issues. I tried both Windows Authentification and local sql account, both are very choppy, sometimes works sometimes doesn't.
TITLE: Connect to Server
Cannot connect to BG-SQL2005.
ADDITIONAL INFORMATION:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An established connection was aborted by the software in your host machine.) (Microsoft SQL Server, Error: 10053)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10053&LinkId=20476
BUTTONS:
OK
I am also getting this error when trying to ALTER one of my stored procs :
A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
Mostlikely the server is closing the connections for some reason, possibly the client does not have permission to access some sqlserver resources, e.g. database, sp, xp. We might get more hint as to why if you could share out the sql server ERRORLOG.|||Here are my logs:http:
aprint screens of various errors I have received on my remote SQL Server 2005 (Enterprise version):
http:
issue resolved, reinstalled SQL Server 2005 completely
thanks for the inputs!