SQL Server Management Studio: web

Showing posts with label web. Show all posts

Friday, March 30, 2012

Migrating from MDF File to SQL Server 2005?

I created a web site using the "personal web site" starter kit with Visual Studio 2005. It created an ASPNET MDF file as well as a Personal.MDF in my App_Data directory.

I want to migrate this site to a production server that does not have SQL Express, but does have a full version of SQL Server 2005.

How do I migrate both the database format (tables and SPs) as well as the data to the SQL Server?

I can't find anything that looks like Enterprise Manager or Query Analyzer on my system, and installing the "native client tools" doesn't do anything except install configuration utilities (no clients).

Inside of Visual Studio 2005, I can bring up both databases (one from the MDF file(s) and one using a connection string to the server), but there doesn't appear to be any way to copy from one to the other.

There must be an easy way to do this, right?

Many thanks in advance!

Hello cambler,

You can simply do a straight-forward Attach Database function in SQL Server 2005 Management Studio. You can simply copy the MDF and LDF files from your App_Data folder from your PC to your production server running SQL Server 2005. Then, attach the database pointing to the copy of the MDF file. You need to detach the database files first on your development PC before you can copy the MDF and LDF files as the service is making use of these files.

For more information, visit http://support.microsoft.com/default.aspx?scid=kb;en-us;224071

|||

I am trying to utilize the SQL Server Management Studio to open an MDF file, so I can perform tasks such as importing CSV files. I guess that I need to attach to a an MDF file, but I don't see the that option available.

If there is a nother approach, please advise.

Thanks,

|||From SQL Server Management Studio, you can simply right-click on the Databases folder and select Attach. Then point to the location of your MDF file. That should do the trick.sql

Migrating from Access, boolean field problem

Hallo,
I am migrating complex database from Access 2000 to MSSQL server 8. This
database is used by web applications. Some time I need to be able swicth
between the old Access version and new SQL server driven one. I have
different connection strings, and connecting works well.
However, some sql query incompatibility has appeared...
Number of Access tables have boolean (Yes/No) fields. In Access, I could run
a query like this:
SELECT id FROM myTable WHERE myBooleanField
it returns all records where myBooleanField value is true. Now, when I
migrated to MSSQL, these boolean fields are of "bit" type, and carry "1" for
every Access "true" value, and "0" for "false" values. With this new field
type, I can no longer run the above mentioned query. I must change it to
this:
SELECT id FROM myTable WHERE myBooleanField=1
Now, this would not be a crazy problem, however I need to be able to run it
for some time on both database solutions, Access and MSSQL, so I really need
to have compatible queries.
One solution I see now would be converting the field type in access from
boolean to byte, and then run the "=1" queries. But that could involve range
of incompatibilities within the application itself, that assumes that these
fields are "true" or "false" instead of "1" and "0". Browsing through the
application to find these places is not really the best thing I can imagine.
So, maybe there is a real "boolean" field in MSSQL? Maybe other approaches
to solve my problem?
Thanks,
PavilsOne issue is that Access/Jet booleans are not true booleans, but can
also contain null values. Change the Jet columns to Not Null and
provide a default value (same with SQLS). This lets you avoid the
three-valued logic trap. In your SQL statements and code, perform all
comparisons to 0, not to -1 or 1 or True or False. 0 is always false,
everywhere, so both engines are going to interpret "<>0" the same way.
-- Mary
MCW Technologies
http://www.mcwtech.com
On Thu, 19 Feb 2004 16:25:28 +0200, "Pavils Jurjans"
<pavils@.mailbox.riga.lv> wrote:
>Hallo,
>I am migrating complex database from Access 2000 to MSSQL server 8. This
>database is used by web applications. Some time I need to be able swicth
>between the old Access version and new SQL server driven one. I have
>different connection strings, and connecting works well.
>However, some sql query incompatibility has appeared...
>Number of Access tables have boolean (Yes/No) fields. In Access, I could run
>a query like this:
>SELECT id FROM myTable WHERE myBooleanField
>it returns all records where myBooleanField value is true. Now, when I
>migrated to MSSQL, these boolean fields are of "bit" type, and carry "1" for
>every Access "true" value, and "0" for "false" values. With this new field
>type, I can no longer run the above mentioned query. I must change it to
>this:
>SELECT id FROM myTable WHERE myBooleanField=1
>Now, this would not be a crazy problem, however I need to be able to run it
>for some time on both database solutions, Access and MSSQL, so I really need
>to have compatible queries.
>One solution I see now would be converting the field type in access from
>boolean to byte, and then run the "=1" queries. But that could involve range
>of incompatibilities within the application itself, that assumes that these
>fields are "true" or "false" instead of "1" and "0". Browsing through the
>application to find these places is not really the best thing I can imagine.
>So, maybe there is a real "boolean" field in MSSQL? Maybe other approaches
>to solve my problem?
>Thanks,
>Pavils
>|||Thanks Mary,
This is a good suggestion, it helps me to move further...
Now another problem has arised:
Access runs this query without complaints:
UPDATE myTable SET myBool = NOT myBool WHERE id=100
What could be a syntax working on both Jet and MSSQL engines?
I tried this one...
UPDATE myTable SET myBool = IIf(myBool, 0, 1) WHERE id=100
but I get error -
'IIf' is not a recognized function name.
Maybe some other smart syntax?
Thanks,
-- Pavils
"Mary Chipman" <mchip@.nomail.please> wrote in message
news:rij9301d0sjh4b3ghkva5vmjh3b3pn7cpp@.4ax.com...
> One issue is that Access/Jet booleans are not true booleans, but can
> also contain null values. Change the Jet columns to Not Null and
> provide a default value (same with SQLS). This lets you avoid the
> three-valued logic trap. In your SQL statements and code, perform all
> comparisons to 0, not to -1 or 1 or True or False. 0 is always false,
> everywhere, so both engines are going to interpret "<>0" the same way.
> -- Mary
> MCW Technologies
> http://www.mcwtech.com
> On Thu, 19 Feb 2004 16:25:28 +0200, "Pavils Jurjans"
> <pavils@.mailbox.riga.lv> wrote:
> >Hallo,
> >
> >I am migrating complex database from Access 2000 to MSSQL server 8. This
> >database is used by web applications. Some time I need to be able swicth
> >between the old Access version and new SQL server driven one. I have
> >different connection strings, and connecting works well.
> >
> >However, some sql query incompatibility has appeared...
> >
> >Number of Access tables have boolean (Yes/No) fields. In Access, I could
run
> >a query like this:
> >
> >SELECT id FROM myTable WHERE myBooleanField
> >
> >it returns all records where myBooleanField value is true. Now, when I
> >migrated to MSSQL, these boolean fields are of "bit" type, and carry "1"
for
> >every Access "true" value, and "0" for "false" values. With this new
field
> >type, I can no longer run the above mentioned query. I must change it to
> >this:
> >
> >SELECT id FROM myTable WHERE myBooleanField=1
> >
> >Now, this would not be a crazy problem, however I need to be able to run
it
> >for some time on both database solutions, Access and MSSQL, so I really
need
> >to have compatible queries.
> >
> >One solution I see now would be converting the field type in access from
> >boolean to byte, and then run the "=1" queries. But that could involve
range
> >of incompatibilities within the application itself, that assumes that
these
> >fields are "true" or "false" instead of "1" and "0". Browsing through the
> >application to find these places is not really the best thing I can
imagine.
> >
> >So, maybe there is a real "boolean" field in MSSQL? Maybe other
approaches
> >to solve my problem?
> >
> >Thanks,
> >
> >Pavils
> >
>|||One thing that's going to continue to trip you up in writing your
queries is not understanding the fundamental differences between
Access SQL and T-SQL, the two main points of which are:
-- Access SQL relies heavily on the expression service and VBA to
compensate for the fact that it has no programming language features
on its own. You can execute VBA functions like Iif inside of a query
only against the Jet engine with Access as a FE. .
-- T-SQL contains many programming language features, like variables.
It does not rely on an external programming language to provide this
functionality the way Access does. When you try VBA syntax, it fails
because SQLS has no knowledge of VBA.
For the most part, you'll want to stay away from language elements
that are specific to either Jet SQL or T-SQL. I'd start by writing the
queries using the Query Analyzer, then copying/pasting them into an
Access query window to see if the syntax works in both. SQL Books
Online is a good reference--Access SQL documentation is practically
non-existant. Besides the language elements, be aware that you're also
going to have problems with delimiters when working with datetime
values -- Jet uses # and SQLS uses '.
-- Mary
MCW Technologies
http://www.mcwtech.com
On Thu, 19 Feb 2004 18:09:50 +0200, "Pavils Jurjans"
<pavils@.mailbox.riga.lv> wrote:
>Thanks Mary,
>This is a good suggestion, it helps me to move further...
>Now another problem has arised:
>Access runs this query without complaints:
>UPDATE myTable SET myBool = NOT myBool WHERE id=100
>What could be a syntax working on both Jet and MSSQL engines?
>I tried this one...
>UPDATE myTable SET myBool = IIf(myBool, 0, 1) WHERE id=100
>but I get error -
>'IIf' is not a recognized function name.
>Maybe some other smart syntax?
>Thanks,
>-- Pavils
>"Mary Chipman" <mchip@.nomail.please> wrote in message
>news:rij9301d0sjh4b3ghkva5vmjh3b3pn7cpp@.4ax.com...
>> One issue is that Access/Jet booleans are not true booleans, but can
>> also contain null values. Change the Jet columns to Not Null and
>> provide a default value (same with SQLS). This lets you avoid the
>> three-valued logic trap. In your SQL statements and code, perform all
>> comparisons to 0, not to -1 or 1 or True or False. 0 is always false,
>> everywhere, so both engines are going to interpret "<>0" the same way.
>> -- Mary
>> MCW Technologies
>> http://www.mcwtech.com
>> On Thu, 19 Feb 2004 16:25:28 +0200, "Pavils Jurjans"
>> <pavils@.mailbox.riga.lv> wrote:
>> >Hallo,
>> >
>> >I am migrating complex database from Access 2000 to MSSQL server 8. This
>> >database is used by web applications. Some time I need to be able swicth
>> >between the old Access version and new SQL server driven one. I have
>> >different connection strings, and connecting works well.
>> >
>> >However, some sql query incompatibility has appeared...
>> >
>> >Number of Access tables have boolean (Yes/No) fields. In Access, I could
>run
>> >a query like this:
>> >
>> >SELECT id FROM myTable WHERE myBooleanField
>> >
>> >it returns all records where myBooleanField value is true. Now, when I
>> >migrated to MSSQL, these boolean fields are of "bit" type, and carry "1"
>for
>> >every Access "true" value, and "0" for "false" values. With this new
>field
>> >type, I can no longer run the above mentioned query. I must change it to
>> >this:
>> >
>> >SELECT id FROM myTable WHERE myBooleanField=1
>> >
>> >Now, this would not be a crazy problem, however I need to be able to run
>it
>> >for some time on both database solutions, Access and MSSQL, so I really
>need
>> >to have compatible queries.
>> >
>> >One solution I see now would be converting the field type in access from
>> >boolean to byte, and then run the "=1" queries. But that could involve
>range
>> >of incompatibilities within the application itself, that assumes that
>these
>> >fields are "true" or "false" instead of "1" and "0". Browsing through the
>> >application to find these places is not really the best thing I can
>imagine.
>> >
>> >So, maybe there is a real "boolean" field in MSSQL? Maybe other
>approaches
>> >to solve my problem?
>> >
>> >Thanks,
>> >
>> >Pavils
>> >
>|||Thanks, Mary for your help
I've been doing databasing in Access, mySQL, and some generic work in
interBase, MSSQL, and Oracle... but in this case I have to port fairly
complex application to MSSQL and I really see all those blanks I miss in the
knowledge about MSSQL. Well, but that's the nature of learning curve, being
very steep :) I'd be happy if this project would be originally developed in
MSSQL, but unfortunately this is not the case.
On my previous query, where I was looking for both Jet and MSSQL engine
compatible syntax for NOT-ting the boolean value, I solved it like this:
UPDATE myTable SET myBool = 1-ABS(myBool) WHERE id=123
That works on both Access and MSSQL.
The date delimiter thing I fortunately have abstracted away in my database
library, so it's easily fixable thing. Some issues about text/BLOB fields
are luring in now, but nothing very crucial though..
Thanks,
Pavils Jurjans
"Mary Chipman" <mchip@.nomail.please> wrote in message
news:7roe30topfasals1m2avf2u2fj3dqol9dn@.4ax.com...
> One thing that's going to continue to trip you up in writing your
> queries is not understanding the fundamental differences between
> Access SQL and T-SQL, the two main points of which are:
> -- Access SQL relies heavily on the expression service and VBA to
> compensate for the fact that it has no programming language features
> on its own. You can execute VBA functions like Iif inside of a query
> only against the Jet engine with Access as a FE. .
> -- T-SQL contains many programming language features, like variables.
> It does not rely on an external programming language to provide this
> functionality the way Access does. When you try VBA syntax, it fails
> because SQLS has no knowledge of VBA.
> For the most part, you'll want to stay away from language elements
> that are specific to either Jet SQL or T-SQL. I'd start by writing the
> queries using the Query Analyzer, then copying/pasting them into an
> Access query window to see if the syntax works in both. SQL Books
> Online is a good reference--Access SQL documentation is practically
> non-existant. Besides the language elements, be aware that you're also
> going to have problems with delimiters when working with datetime
> values -- Jet uses # and SQLS uses '.
> -- Mary
> MCW Technologies
> http://www.mcwtech.com

Migrating from Access, boolean field problem

I'd be happy if this project would be originally developed in
MSSQL, but unfortunately this is not the case.
On my previous query, where I was looking for both Jet and MSSQL engine
compatible syntax for NOT-ting the boolean value, I solved it like this:
UPDATE myTable SET myBool = 1-ABS(myBool) WHERE id=123
That works on both Access and MSSQL.
The date delimiter thing I fortunately have abstracted away in my database
library, so it's easily fixable thing. Some issues about text/BLOB fields
are luring in now, but nothing very crucial though..
Thanks,
Pavils Jurjans
"Mary Chipman" <mchip@.nomail.please> wrote in message
news:7roe30topfasals1m2avf2u2fj3dqol9dn@.
4ax.com...
> One thing that's going to continue to trip you up in writing your
> queries is not understanding the fundamental differences between
> Access SQL and T-SQL, the two main points of which are:
> -- Access SQL relies heavily on the expression service and VBA to
> compensate for the fact that it has no programming language features
> on its own. You can execute VBA functions like Iif inside of a query
> only against the Jet engine with Access as a FE. .
> -- T-SQL contains many programming language features, like variables.
> It does not rely on an external programming language to provide this
> functionality the way Access does. When you try VBA syntax, it fails
> because SQLS has no knowledge of VBA.
> For the most part, you'll want to stay away from language elements
> that are specific to either Jet SQL or T-SQL. I'd start by writing the
> queries using the Query Analyzer, then copying/pasting them into an
> Access query window to see if the syntax works in both. SQL Books
> Online is a good reference--Access SQL documentation is practically
> non-existant. Besides the language elements, be aware that you're also
> going to have problems with delimiters when working with datetime
> values -- Jet uses # and SQLS uses '.
> -- Mary
> MCW Technologies
> http://www.mcwtech.com|||Pavil,
I've been in this situation many times. As has been mentioned already, Acces
s'
YES/NO field is really a three-state field: YES/NO/NULL, where in SQL SERVER
the BIT type is 2-state.
The other problem is that Access treats TRUE as -1 where SQL Serrver actuall
y
treats TRUE as any non-zero value.
Armed with that information, you have two choices:
1) Use INT field in SQL Server, and you'll see good ol' -1 and 0 in that tab
le
anytime Access gets its ODBC/JET mitts on it.
2) When creating WHERE clauses in Access, get in the habit of ALWAYS using t
he
following test for TRUE:
Fld <> 0
Do that in VBA too, just to be consistent.

Migrating from Access to SQL Server with a web front end

Afternoon all,

Apologies for cross-posting but as my query covers both Access and SQL
Server I thought I'd send it both!

I have inherited a project to migrate a fairly complex series of
Access databases into a single proper SQL database with a web front
end.

Its quite a nasty job as people are working on a variety of data sets
at several Universities around the world and the data has got very
messy; hence the requirement to put it all on one live web enabled
database server and provide a web-based front end (particularly as
some users insist on using Macs so can't run Access as a front end
anyway).

If anyone could give me hints on how to perform such a migration or if
anyone knows of any good books or other documents on this I'd be
grateful for assistance.

Many thanks

Rich May
Museum of LondonFirst off, congratulations - this is a great move to make.

As far as converting the tables, use DTS (Data Transformation Services) in
sql server. It is pretty much wizard driven and works really well. As for
the queries, you would do best to forget you even have them in Access and
rewrite everything using Stored Procedures. My favorite book for "stepping"
between access and sql server is "Microsoft Access Developer's Guide to SQL
Server" by Chipman and Baron. It's wonderful.

As for your web front end... that is where the headache starts. You can
pretty much choose two paths if you want to stay on the Microsoft path. You
can do it using ASP or ASP.NET. Both will run on IIS (.net needs framework
installed).

If you are serving to Macs, you may deliver your app better using ASP
because you will be able to better control the rendered output (very good
for Netscape). I use Visual Basic to build "ActiveX DLL" components to
alleviate the complexity of the ASP pages so you would want to be proficient
in Visual Basic and instantiating COM components. Next, you need to take
ADO (ActiveX Data Objects) head on and learn it well, that is what you will
use to connect to sql, execute queries, and work with data.

If you are using IE on all clients and have control over them, you will find
that Visual Studio.NET does a great job at deploying web applications in
ease and speed, once you pass the high learning curve. I VERY highly
recommend "Programming Microsoft Visual Basic .Net" by Francesco Balena
(1600 pages).

If it all sounds complex, don't get me wrong... it is. If you need help,
let me know, we do this for a living.

--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz

"Rich May" <rmay@.museumoflondon.org.uk> wrote in message
news:e12c70e0.0311140943.722ed0ba@.posting.google.c om...
> Afternoon all,
> Apologies for cross-posting but as my query covers both Access and SQL
> Server I thought I'd send it both!
> I have inherited a project to migrate a fairly complex series of
> Access databases into a single proper SQL database with a web front
> end.
> Its quite a nasty job as people are working on a variety of data sets
> at several Universities around the world and the data has got very
> messy; hence the requirement to put it all on one live web enabled
> database server and provide a web-based front end (particularly as
> some users insist on using Macs so can't run Access as a front end
> anyway).
> If anyone could give me hints on how to perform such a migration or if
> anyone knows of any good books or other documents on this I'd be
> grateful for assistance.
> Many thanks
> Rich May
> Museum of London|||several choices, depending on what you're comfy with ..
1) sql server, IIS & ASP
2) mySQL, apache, php

here's a RAD tool that I found the other day to create web pages for
either option (I haven't tried it yet)
http://www.citybusinesslogic.com/apwab.php

and somewhere I've got vba code to convert ms-access tables to mysql
format

rmay@.museumoflondon.org.uk (Rich May) wrote in message news:<e12c70e0.0311140943.722ed0ba@.posting.google.com>...
> Afternoon all,
> Apologies for cross-posting but as my query covers both Access and SQL
> Server I thought I'd send it both!
> I have inherited a project to migrate a fairly complex series of
> Access databases into a single proper SQL database with a web front
> end.
> Its quite a nasty job as people are working on a variety of data sets
> at several Universities around the world and the data has got very
> messy; hence the requirement to put it all on one live web enabled
> database server and provide a web-based front end (particularly as
> some users insist on using Macs so can't run Access as a front end
> anyway).
> If anyone could give me hints on how to perform such a migration or if
> anyone knows of any good books or other documents on this I'd be
> grateful for assistance.
> Many thanks
> Rich May
> Museum of London|||Hi Rich,

I think there are 3 options. a) Access' Upsizing Migration Wizard
b)Sql Server's DTS and c) setting Access as a linked server and
programmatically importing the data. I believe the main problem
you'll run into is that Access' datatypes are not 100% compatible with
Sql server's. - Louis|||louisducnguyen@.hotmail.com (louis nguyen) wrote in message news:<b0e9d53.0311142220.41dff853@.posting.google.com>...
> Hi Rich,
> I think there are 3 options. a) Access' Upsizing Migration Wizard
> b)Sql Server's DTS and c) setting Access as a linked server and
> programmatically importing the data. I believe the main problem
> you'll run into is that Access' datatypes are not 100% compatible with
> Sql server's. - Louis

Another problem I have seen with the upsize wizard is it makes all
columns with the type nvarchar i.e. unicode which doubles the space
requirements.

Duncan|||"duncan" wrote

> Another problem I have seen with
> the upsize wizard is it makes all
> columns with the type nvarchar i.e.
> unicode which doubles the space
> requirements.

First, I don't think that is true -- all _text_ columns, perhaps, but
certainly not numeric and date/time columns.

Secondly, were you under the impression that Access does NOT use unicode? It
has since Access 2000. There is an option for "unicode compression" to
reduce the impact; I don't know if there is such an option in SQL Server,
but would think that it would have a similar feature.

Larry Linson
Microsoft Access MVP|||Is Cold Fusion a viable alternative to ASP in this kind of situation?

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!|||In Ms SQL...

Char is fixed length and pads with spaces
NChar is fixed length and pads with spaces, plus is unicode
VarChar is variable character (with max length spec)
NVarChar is variable (maxlength), plus is unicode

Since I don't deploy to any other language and don't plan to, I never use
the N' datatypes.

Also in SQL, the "SmallDateTime" field type is 4 bytes and the "DateTime" is
8 bytes). If it's 4 bytes in Access, then the equiv is "SmallDateTime".

In SQL Numeric DT's, there is tinyint, smallint, int, real, bigint, float,
money, smallmoney, and decimal. All with their mix of capacity.

--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz

"Larry Linson" <bouncer@.localhost.not> wrote in message
news:bpytb.58064$p9.53071@.nwrddc02.gnilink.net...
> "duncan" wrote
> > Another problem I have seen with
> > the upsize wizard is it makes all
> > columns with the type nvarchar i.e.
> > unicode which doubles the space
> > requirements.
> First, I don't think that is true -- all _text_ columns, perhaps, but
> certainly not numeric and date/time columns.
> Secondly, were you under the impression that Access does NOT use unicode?
It
> has since Access 2000. There is an option for "unicode compression" to
> reduce the impact; I don't know if there is such an option in SQL Server,
> but would think that it would have a similar feature.
> Larry Linson
> Microsoft Access MVP|||Sure, I looked into it some time ago when I was a beginner, but then I
discovered the unimaginable amount of documentation and books from multiple
authors in Microsoft products and I didn't even give it a second thought.
To me, no product is satisfactory if I have to spend days looking for
answers, and especially when they aren't there to be found.

--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz

"John Callaghan" <jackit2@.yahoo.com> wrote in message
news:3fb88be3$0$194$75868355@.news.frii.net...
> Is Cold Fusion a viable alternative to ASP in this kind of situation?
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!|||In my experience, the data conversion part of a project like this is almost
trivial compared to the front-end application challenge.

Access forms and reports can be incredibly complex, with subforms, simple
data binding, no-code dynamic behavior (record navigation, filtering,
sorting, finding, column-reordering, all those are built in to Access, not
at all in asp), and the list goes on and on. If your Access front-end
application is complex, it could be impossibly time-consuming to do in asp,
slightly less so in asp.net.

You would need some other tool for reporting (Crystal or others), I've made
crude html reports in asp and it is nearly impossible to do even the easy
stuff Access reports can do.

As a example, I wrote a full maintenance application for a 30 table database
(with lots of RI between tables), with multiple subforms, dropdown
navigation, and lots of other features, all in one day of work.. ASP would
have taken weeks to do even close to the same functionality.

So overall, my suggestion is if the Access forms are complex, plan for 1000
to 2000% more development time over Access forms. You will definitely need a
better reporting tool than html/asp. Hope this helps,

Steve Nyberg

Monday, March 26, 2012

Migrated from SQL 2k5 Express to SQL Server - Profile doesn't work

I recently created an application that stores 3 variables in the web.config in the "Profile"configuration:

By doing this my web.config automatically configured itself to create a database in my app_data folder and also filled in all the table rows as necessary. Then I moved the code to my sql server running SQL Server 2005 Standard and found out that it won't generate that database in either the app_data folder or the SQL Server Data directory. I've gotten so desperate to get this database created that I've (temporarily) given "Everyone" full permissions to both directories. I then double checked that my named pipes to that server were enabled, and then also tried moving my database from my working sql express app from a different computer to the server. I still cannot get it to work.

If I have no database in the folders that worked on sql express i get this error:

"SQLExpress database file auto-creation error:
The connection string specifies a local Sql Server Express ..."

If I have a database in the folder it says it can't communicate with it or can't find it.

My web.config shows:

Is there a way to successfully generate this database with sql server? Please Help!!!

I figured the problem out...

For those of you interested, here is the solution. I found on google groups early on when i had this problem, but it didn't work and I never payed attention to the error I got, I just assumed it couldn't work. Then I figured i'd give it another shot. The trick is to make sure you don't include the line breaks in your web.config when replaceing the suggested code. Anyway, below is the link (solution provided by Brad Hammond):

http://groups.google.com/group/microsoft.public.sqlserver.programming/browse_thread/thread/5370c080936fda9b/5d39f0c6bf9f45dd?lnk=st&q=%22sql+server+2005%22+profile&rnum=9#5d39f0c6bf9f45dd

My machine.config solution:
<add name="LocalSqlServer" connectionString="data source=.\West;Initial Catalog=ASPNETDB;User ID=UserName;password=Password" />

Thank you Brad, Hope this helps other people out!

Friday, March 23, 2012

Migrate subset of data from 2000 to 2005

First a little background.

Production server is SQL Server 2000. Various clients will be installing a desktop version of our web application. The desktop app will be running SQL Server 2005 Express (MSDE replacement, correct?). When the client downloads the package, the installer will import their data from the SQL Server 2000 production database into the SQL Server 2005 database. The production database contains numerous clients, so it doesn't make sense to migrate ALL of the data, only the data that belongs to the client.

My question is what method(s) would allow this to be done? The databases will NOT be connected to one another so using DTS packages is not an option.

After doing some research I came to the conclusion that the only way I could see this working, would be to output each tables data (just the data that belongs to the particular client) into its own text file and then import them individually on the SQL Server 2005 side.

Does anyone have any other ideas?

Kevin - I have the same dilemma currently and wondered if you had found a solution to this?

migrate SQL server 2000 DB on hosted environment to SQL 2k5 express

I have web application and sql server 2k database in hosted environment. How can migrate my database to another server where I have SQL Server Express 2005.
I cant take backup or I cant stop the server as it is hosted environment sharing many databases. Note that I dont want to loose single transaction in this process..Is there any way to do this.

Thanks in advance

I suspect you're going to have to accept some window of downtime to accomplish the upgrade. You might post a question to the database engine forum about ways to minimize the downtime, as this is a common sort of request.

migrate SQL server 2000 DB on hosted environment to SQL 2k5 express

Thanks in advance

sql

Monday, March 12, 2012

Migrate database from MS Access to SQL Server 2000

Hi All,
I had installed Internet Information Sevices (IIS) on
Windows 2000 to simulate a web server. The ASP code to
open the Access database is:
Set db = Server.CreateObject("ADODB.Connection")
db.open "Driver={Microsoft Access Driver (*.mdb)}; DBQ="
&server.MapPath("../data/test.mdb")&";"
The code works fine on IIS and Access database. Then I
installed the SQL Server 2000 and changed the ASP code to:
Set db = Server.CreateObject("ADODB.Connection")
db.open "DRIVER={SQL
Server};SERVER=myPC;UID=sa;PWD=myPasswd;DATABASE=test"
dbsql="Y"
Where "myPC" is the computer name, "myPasswd" is the
password for user "sa". But the ASP code did not work.
Anything wrong?
Thanks in advance.> But the ASP code did not work.
You're going to have to be more specific.|||what error do u get'
--
Shaju Thomas
"Nancy" <nlan2000@.hotmail.com> wrote in message
news:063401c39b88$7ea843c0$a301280a@.phx.gbl...
> Hi All,
> I had installed Internet Information Sevices (IIS) on
> Windows 2000 to simulate a web server. The ASP code to
> open the Access database is:
> Set db = Server.CreateObject("ADODB.Connection")
> db.open "Driver={Microsoft Access Driver (*.mdb)}; DBQ="
> &server.MapPath("../data/test.mdb")&";"
> The code works fine on IIS and Access database. Then I
> installed the SQL Server 2000 and changed the ASP code to:
> Set db = Server.CreateObject("ADODB.Connection")
> db.open "DRIVER={SQL
> Server};SERVER=myPC;UID=sa;PWD=myPasswd;DATABASE=test"
> dbsql="Y"
> Where "myPC" is the computer name, "myPasswd" is the
> password for user "sa". But the ASP code did not work.
> Anything wrong?
> Thanks in advance.
>|||Hi all,
Thanks for your kindness help.
The error message says:
HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services
Error Type:
ADODB.Recordset (0x800A0E7D)
The connection cannot be used to perform this operation.
It is either closed or invalid in this context.
Which referred to the following code:
set rs=Server.CreateObject("ADODB.Recordset")
The reason is the database connection was not set up
successfully, where the cause was actually a typo in the
server name. It works now after I corrected it.
But thanks anyway!
Nancy
>--Original Message--
>Hi All,
>I had installed Internet Information Sevices (IIS) on
>Windows 2000 to simulate a web server. The ASP code to
>open the Access database is:
>Set db = Server.CreateObject("ADODB.Connection")
>db.open "Driver={Microsoft Access Driver (*.mdb)}; DBQ="
>&server.MapPath("../data/test.mdb")&";"
>The code works fine on IIS and Access database. Then I
>installed the SQL Server 2000 and changed the ASP code to:
>Set db = Server.CreateObject("ADODB.Connection")
>db.open "DRIVER={SQL
>Server};SERVER=myPC;UID=sa;PWD=myPasswd;DATABASE=test"
>dbsql="Y"
>Where "myPC" is the computer name, "myPasswd" is the
>password for user "sa". But the ASP code did not work.
>Anything wrong?
>Thanks in advance.
>.
>|||did u open the connection
--
Shaju Thomas
"Nancy" <nlan2000@.hotmail.com> wrote in message
news:055a01c39d0b$9fc67390$a601280a@.phx.gbl...
> Hi all,
> Thanks for your kindness help.
> The error message says:
> HTTP 500.100 - Internal Server Error - ASP error
> Internet Information Services
> Error Type:
> ADODB.Recordset (0x800A0E7D)
> The connection cannot be used to perform this operation.
> It is either closed or invalid in this context.
> Which referred to the following code:
> set rs=Server.CreateObject("ADODB.Recordset")
> The reason is the database connection was not set up
> successfully, where the cause was actually a typo in the
> server name. It works now after I corrected it.
> But thanks anyway!
> Nancy
>
> >--Original Message--
> >Hi All,
> >
> >I had installed Internet Information Sevices (IIS) on
> >Windows 2000 to simulate a web server. The ASP code to
> >open the Access database is:
> >
> >Set db = Server.CreateObject("ADODB.Connection")
> >db.open "Driver={Microsoft Access Driver (*.mdb)}; DBQ="
> >&server.MapPath("../data/test.mdb")&";"
> >
> >The code works fine on IIS and Access database. Then I
> >installed the SQL Server 2000 and changed the ASP code to:
> >
> >Set db = Server.CreateObject("ADODB.Connection")
> >db.open "DRIVER={SQL
> >Server};SERVER=myPC;UID=sa;PWD=myPasswd;DATABASE=test"
> >dbsql="Y"
> >
> >Where "myPC" is the computer name, "myPasswd" is the
> >password for user "sa". But the ASP code did not work.
> >
> >Anything wrong?
> >
> >Thanks in advance.
> >
> >.
> >

Migrate ASP .net web site from sql 2005 express to sql 2005 standard edition

Dear all,

I've been using ASP.NET with SQL 2005 express for several months and everything has been fine. Now a customer asks me to install my application on an already existant instance of SQL Server standard edition.

I was not able to use nor my application, neither a HelloWorld example.

I created a simple Default.aspx that uses a simple database with a single table "Person" via a standard gridview. When I try to open the page I receive an error wich informs me that NT Network service is not able to access database.

I've been searching on google for hours and I've tryed unsuccessfully several different way.

Can anyone suggest me a scientific procedure to migrate an ASP .net web site from sql 2005 express to sql 2005 standard ?

Thank you very Much

Fabrizio

As I know the only think you have to change is a connection string because SQL express uses different syntax for it. You can move your database to SQL server standard just by connecting it to server, you have to create your users and give them correct rights, you also have to create ASP DB if you would like to use ASP authentication finally modify your connections stirings to point to SQL server not to local SQL server express file.

There are a lot of post about this on this ASP forum.

Good luck

Migrate

I have developed a web application using MSDE. I do not have sql 2000. I now have to transfer this database to an asp host.
Is there a DTS package or osql commands that I can export the entire database sp and all to a sql script file.

Regards
S(:You can create scripts for all of the database objects (tables, view, sprocs, etc.) but I don't believe you can create scripts for the data too. You can use DTS to copy the data, however, after you create the objects.

I haven't tried this with MSDE but with Sql Server databases you can detach them from your local database and physically copy the database files to the remote destination and then re-attach them there. The database has to be compatible with where you are attaching it and whether it considers MSDE files compatible is the question.

Friday, March 9, 2012

Microsofts Sql web admin and sqldmo

Hello all,

has anyone had the opportunity to try the sql web admin tool? if so, i have one question.

How can i use this to connect to a remote sql/msde server?

in the server textbox on the login screen i try 'machine name'\'instance name', along with the sa username and password. This does not work however.

am i just entering the wrong value , or do i need to change the code of the .connect method to allow for remote connections?

TIA.

-C-By "does not work", do you mean you are getting an error?

I have been successful using Web Data Administrator to connect to a remote database. The remote database must have mixed authentication (SQL Server and Windows). and you must be using a valid login and password. I accessed the server using the IP address.

As an additional point, I was VPN authenticated on the remote network before connecting.

Terri

Microsoft.Reporting.WebForms.ReportViewer does not contain a definition for Reset

Hi everyone I developed a web form with a report viewer. I change the report datasource and report path based on user input. Before i do anything on the report i first reset it with this line:

rvWaitTime.Reset();

And then set the parameters, datasources, etc. It works fine on my dev machine: Windows Vista with .NET 2.0 installed (.NET 3.0 is installed as well). When I move the code to the production box: Windows Server 2003 with .NET 2.0 and 3.0 installed i get this error:

'Microsoft.Reporting.WebForms.ReportViewer' does not contain a definition for 'Reset'

and of course it fails on the line of code mentioned above.

Any ideas?

Who would have thought that you needed a seperate installation for a control that comes built in with VS 2005? I finally solved the problem. I needed to install theMicrosoft Report Viewer Redistributable 2005 SP1 (Full Installation) on my server and now everything works like a charm!

Wednesday, March 7, 2012

Microsoft Word Delivery Extension & Use of web client

1. Is there a Microsoft Word or RTF delivery extension available for SQL
Reporting Services?
If not, is there any technique of producing the same with XML and XSLT?
2. To solve the security extension problem on a standard edition:
I am thinking of using web client on a filter page on the web server to
connect to the reporting server so that I don't bypass the web server when a
URL access request comes thru.
I mean, the URL for the report viewer won't be reporting server, instead it
will be an aspx (filter) page within the web server. The filter on the web
server will intercept and in turn impersonate a user on the report server and
render a report in the report viewer.
My question: I have not used web clients from web server before. Will it
affect the performance of web server? Is the above theory make sense at all?
I haven't implemented it.
Thanks,
Sri.The XML/XSLT idea is probably your best bet. Years ago I created a custom
RTF generator (to create nice-looking documents from a CASE tool). It's
easy once you do two things:
(1) Hunt down the RTF specification (from Microsoft I think), and learn the
basic syntax.
(2) Create a Word document that looks like what you want and save it to RTF
as a baseline/reference.
Then, you'll be armed and dangerous -- especially if you know how to do
XSLT.
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Sri" <Sri@.discussions.microsoft.com> wrote in message
news:8B848583-4F7E-490F-9E77-95CD40C30072@.microsoft.com...
> 1. Is there a Microsoft Word or RTF delivery extension available for SQL
> Reporting Services?
> If not, is there any technique of producing the same with XML and XSLT?
> 2. To solve the security extension problem on a standard edition:
> I am thinking of using web client on a filter page on the web server to
> connect to the reporting server so that I don't bypass the web server when
> a
> URL access request comes thru.
> I mean, the URL for the report viewer won't be reporting server, instead
> it
> will be an aspx (filter) page within the web server. The filter on the web
> server will intercept and in turn impersonate a user on the report server
> and
> render a report in the report viewer.
> My question: I have not used web clients from web server before. Will it
> affect the performance of web server? Is the above theory make sense at
> all?
> I haven't implemented it.
> Thanks,
> Sri.
>|||Thanks Jeff. I will investigate.
"Jeff A. Stucker" wrote:
> The XML/XSLT idea is probably your best bet. Years ago I created a custom
> RTF generator (to create nice-looking documents from a CASE tool). It's
> easy once you do two things:
> (1) Hunt down the RTF specification (from Microsoft I think), and learn the
> basic syntax.
> (2) Create a Word document that looks like what you want and save it to RTF
> as a baseline/reference.
> Then, you'll be armed and dangerous -- especially if you know how to do
> XSLT.
> --
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "Sri" <Sri@.discussions.microsoft.com> wrote in message
> news:8B848583-4F7E-490F-9E77-95CD40C30072@.microsoft.com...
> > 1. Is there a Microsoft Word or RTF delivery extension available for SQL
> > Reporting Services?
> >
> > If not, is there any technique of producing the same with XML and XSLT?
> >
> > 2. To solve the security extension problem on a standard edition:
> >
> > I am thinking of using web client on a filter page on the web server to
> > connect to the reporting server so that I don't bypass the web server when
> > a
> > URL access request comes thru.
> > I mean, the URL for the report viewer won't be reporting server, instead
> > it
> > will be an aspx (filter) page within the web server. The filter on the web
> > server will intercept and in turn impersonate a user on the report server
> > and
> > render a report in the report viewer.
> >
> > My question: I have not used web clients from web server before. Will it
> > affect the performance of web server? Is the above theory make sense at
> > all?
> > I haven't implemented it.
> >
> > Thanks,
> > Sri.
> >
>
>|||Hi,
You can check http://officewriter.softartisans.com/officewriter-250.aspx
for the first question.
creating a 'filter' will not affect performance
--
Message posted via http://www.sqlmonster.com

Microsoft Web Data Administrator, hangs on log in

Hi
I have downloaded MS Web Data Administrator to conenct to my MSDE
database. It hangs when i login using "SQL Login"
When i open up Web Data Administrator, it defaults to Port 80 and
Cassini Personal Web Server (the "IIS" button has been disabled).
Once I start Web DA with this information, and enter in the following
under an "SQL login"
Username: sa
Password: ****
Server: myServerName\myMSDEDatabase
and press "Login" it does nothing (seems to hang) and im left on the
log in page...I never get an error message, it just keeps on trying to
log in, i presume.
I am running MSDE on Win 2000 Server. MSDE is set up to use SQL
authentication (instead of Windows)
Any suggestions?
--Pam
Hi, I found this floating around on the web and did as it instructed,
but it still doesn't work!
___________________________________________
Christopher Hill Feb 7, 6:40 am show options
Newsgroups: microsoft.public.sqlserver.msde
From: "Christopher Hill" <min...@.ntlworld.com> - Find messages by this
author
Date: Mon, 7 Feb 2005 03:40:46 -0800
Local: Mon,Feb 7 2005 6:40 am
Subject: SOLUTION: SQL Web Data Administrator hangs on login
Reply to Author | Forward | Print | View Thread | Show original |
Report Abuse
(Also posted to
http://register.microsoft.com/=ADmswish/suggestion.asp)
The SQL Web Data Administrator (available here:
http://www.microsoft.com/downl=ADoad...C03=AD9A798-C=
57...
2A332CB7F959&displaylang=3Den) is a very useful tool, but
there is a problem when it is installed with the .net
Framework 1.1 with Service Pack 1. The copy of
WebUIValidation.js that is included with the Web Data
Administrator is out of date and means that it hangs when
you click the 'login' button. If you copy the updated
WebUIValidation.js file from
WINDOWS\Microsoft.NET\Framewor=ADk\v1.1.4322
\ASP.NETClientFiles into {SQL Web Administrator
installation path}\Web\aspnet_client\system=AD_web\1_1_4322\
then the problem with hanging is instantly solved.
Message to Microsoft: Please could you update the SQL Web
Administrator package to fix this problem?
By the way, this is not my solution - I found it on
http://sqljunkies.com/Forums/S=ADhow...PostID=3D2084.
|||Oops, ID-10-T error (IDIOT error!)

the fix I posted above does work, I must have been copying it in the
wrong spot or the copy hadn't "kicked in" just yet.
But the fix truly does work!
--Pam

Microsoft Web Data Administrator

I have download this Front End because MSDE doesnt ship with an Visual
Interface,
i have installed MSDE2000 i believe is MSDE200a
when i installed i pass the SAPWD parameters to the setup and all was
fine...
but i cant loggin with the user SA with no password.
Even if i made an UDL File, i cant connect with that user, i have to check
login USING WINDOWS NT Integrated Security...
:S
how can i connect with the SA user with no password
________________________________
Juan Carlos Garcia
Santo Domingo, Republica Dominicana
hi Juan,
"Juan Carlos Garcia" <AskMePlease@.AskMePlease.Com> ha scritto nel messaggio
news:O%23buOQdmEHA.704@.TK2MSFTNGP09.phx.gbl...
> I have download this Front End because MSDE doesnt ship with an Visual
> Interface,
> i have installed MSDE2000 i believe is MSDE200a
> when i installed i pass the SAPWD parameters to the setup and all was
> fine...
> but i cant loggin with the user SA with no password.
> Even if i made an UDL File, i cant connect with that user, i have to check
> login USING WINDOWS NT Integrated Security...
> :S
> how can i connect with the SA user with no password
if you can not connect using SQL Server authentication at all, this usually
means that only Windows Authentication is enabled for that instance, and you
have to manually enable it, modifying a Windows registry key, as explained
in http://support.microsoft.com/default...b;en-us;285097
if you can connect with SQL Server authentication, but want to clear the sa
password to a blank password, you can execute
EXEC sp_password @.new = 'am301065' , @.loginame = 'sa'
but I strongly warn you not to do it... a strong password always is your
best friend
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Jaun
Doesn't MSDE2000a include SP3a and doesn't SP3a not work with blank passwords?
Rich
"Andrea Montanari" wrote:

> hi Juan,
> "Juan Carlos Garcia" <AskMePlease@.AskMePlease.Com> ha scritto nel messaggio
> news:O%23buOQdmEHA.704@.TK2MSFTNGP09.phx.gbl...
> if you can not connect using SQL Server authentication at all, this usually
> means that only Windows Authentication is enabled for that instance, and you
> have to manually enable it, modifying a Windows registry key, as explained
> in http://support.microsoft.com/default...b;en-us;285097
> if you can connect with SQL Server authentication, but want to clear the sa
> password to a blank password, you can execute
> EXEC sp_password @.new = 'am301065' , @.loginame = 'sa'
> but I strongly warn you not to do it... a strong password always is your
> best friend
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Thks.. for the help for both of you... but finally i have to Uninstall and
Install again passing this parameters : setup SAPWD = "****"
SECURITYMODE=SQL
and know its working... :D
thks.. again... see you..
________________________________
Juan Carlos Garcia
Santo Domingo, Republica Dominicana
"Richard Yeo" <RichardYeo@.discussions.microsoft.com> escribi en el mensaje
news:D66748B5-F213-4251-9B5F-E050B681AD08@.microsoft.com...
> Jaun
> Doesn't MSDE2000a include SP3a and doesn't SP3a not work with blank
passwords?[vbcol=seagreen]
> Rich
>
> "Andrea Montanari" wrote:
messaggio[vbcol=seagreen]
check[vbcol=seagreen]
usually[vbcol=seagreen]
you[vbcol=seagreen]
explained[vbcol=seagreen]
sa[vbcol=seagreen]
|||hi Richard,
"Richard Yeo" <RichardYeo@.discussions.microsoft.com> ha scritto nel
messaggio news:D66748B5-F213-4251-9B5F-E050B681AD08@.microsoft.com...
> Jaun
> Doesn't MSDE2000a include SP3a and doesn't SP3a not work with blank
passwords?
yes it does, but, at install time, you have to force the BLANKSAPWD=1
parameter in order to accept it... an again, I strongly recommend not to
allow blank pwd policies
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Friday, February 24, 2012

Microsoft SQL Web Data Administrator

I have installed this and I cannot access my MSDE Instance. Any ideas?
The instance of my DB is running.
My Server Manager Says that it is running, Services says that it is running,
but I cannot get to the SQLServer (On my own pc) with the Web Data
Administrator or TOAD for SQL Server.
|||It is quite possible that it is running on a non-standard port not 1433.
Open up a console window and type following
PROMPT> telnet localhost 1433
if you see a blank screen that means the server is listening. If you get
an error that means that it is listening on a different port
Joe Tobey wrote:
> I have installed this and I cannot access my MSDE Instance. Any ideas?
> The instance of my DB is running.
|||It is listen in on a different PORT...how do I change that?
"Dennis Black" wrote:

> It is quite possible that it is running on a non-standard port not 1433.
> Open up a console window and type following
> PROMPT> telnet localhost 1433
> if you see a blank screen that means the server is listening. If you get
> an error that means that it is listening on a different port
>
> Joe Tobey wrote:
>
>
|||To determine the port MSDE is using, run the SQL Server Network Utility
on the machine hosting the MSDE instance. The SQL Server Network
Utility can be found at \Program Files\Microsoft SQL
Server\80\Tools\Binn\svrnetcn.exe.
On the general tab, select the your MSDE instance. Select TCP/IP and
press the Properties button and look at the port
Dennis
Joe Tobey wrote:[vbcol=seagreen]
> It is listen in on a different PORT...how do I change that?
> "Dennis Black" wrote:
>

Monday, February 20, 2012

Microsoft SQL Server sq

I took over a website for another consultant. This web site has a sql server database. I can ftp my programs to the site and run them, but I am not sure how I look at the data on the server database with Microsoft SQL Server Management Studio Express. How do I tell smse where the database is located?

Thanks

you would simply enter the IP address of the server the runs the site (and presumably the sql server).

2 things you might have problems with....

(1) is the server running Sql Server 2005 (Express)?

(2) if you still cant connect its possible that there is a firewall in the server that is blocking the connection.

|||

Thanks,

I will give it a try today and let you know.

Microsoft SQL Server sq

Thanks

you would simply enter the IP address of the server the runs the site (and presumably the sql server).

2 things you might have problems with....

(1) is the server running Sql Server 2005 (Express)?

(2) if you still cant connect its possible that there is a firewall in the server that is blocking the connection.

|||

Thanks,

I will give it a try today and let you know.

Microsoft SQL Server Management Express...help

Hi,

im trying to learn SQL Server Management Express

know a good place to start?

Im trying to upload an sql database from Visual Web Developer

Ive been told that this can be done using SQL Server manegement express...

cant see how to import into it yet... any ideas?

With Express you won't be able to upload it directly. What you'll have to do is script the database, then run the script on the production server. This will not keep the data around though. "Script Database as Create to", when you right click on the database. The "real" version of the tool (as opposed to Express) has more features.

If you want to deploy a database, try this (I haven't tried it, but it looks promising)

http://forums.asp.net/thread/1431636.aspx

|||Hi~ What do you mean by 'Upload", if you need the data, you can attach the database files (.mdf and .ldf) in Management Studio. Open it -> Right click on 'Databases' -> Attach...

Friday, March 30, 2012

Migrating from MDF File to SQL Server 2005?

Migrating from Access, boolean field problem

Migrating from Access, boolean field problem

Migrating from Access to SQL Server with a web front end

Monday, March 26, 2012

Migrated from SQL 2k5 Express to SQL Server - Profile doesn't work

Friday, March 23, 2012

Migrate subset of data from 2000 to 2005

migrate SQL server 2000 DB on hosted environment to SQL 2k5 express

migrate SQL server 2000 DB on hosted environment to SQL 2k5 express

Monday, March 12, 2012

Migrate database from MS Access to SQL Server 2000

Migrate ASP .net web site from sql 2005 express to sql 2005 standard edition

Migrate

Friday, March 9, 2012

Microsofts Sql web admin and sqldmo

Microsoft.Reporting.WebForms.ReportViewer does not contain a definition for Reset

Wednesday, March 7, 2012

Microsoft Word Delivery Extension & Use of web client

Microsoft Web Data Administrator, hangs on log in

Microsoft Web Data Administrator

Friday, February 24, 2012

Microsoft SQL Web Data Administrator

Monday, February 20, 2012

Microsoft SQL Server sq

Microsoft SQL Server sq

Microsoft SQL Server Management Express...help

SQL Server Management Studio

Blog Archive

About Me